pgsql-bugs - October 2020

If you find a bug, please use the bug reporting form.

Search the Archives

(enter a message-id to go directly to that message)
Advanced Search

Browse Archives

Prev | Next
Jump to day: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Oct. 1, 2020

Thread Author Time
Re: BUG #16419: wrong parsing BC year in to_date() function Robert Haas 00:24
Re: BUG #16419: wrong parsing BC year in to_date() function David G. Johnston 00:38
Re: BUG #16419: wrong parsing BC year in to_date() function Tom Lane 00:40
Re: BUG #16636: Upper case issue in JSONB type ChandraKumar Ovanan 06:23
Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop Peter Eisentraut 17:22
Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop Peter Eisentraut 17:24
Re: BUG #16641: Postgresql driver 42.2.15 and 42.2.16 has problems connecting to AWS RDS Postgresql database Dave Cramer 23:04

Oct. 2, 2020

Thread Author Time
Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop 📎 Alvaro Herrera 00:08
Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop Tom Lane 01:19
Re: BUG #16641: Postgresql driver 42.2.15 and 42.2.16 has problems connecting to AWS RDS Postgresql database Flemming Rene Jønsson 05:22
BUG #16651: could rename global.tmp to global.stat due to permission denied PG Bug reporting form 09:10
Re: BUG #16519: SET SESSION ROLE in plpgsql requires string literal. 📎 David G. Johnston 20:11

Oct. 3, 2020

Thread Author Time
Unnecessary FOR UPDATE lock instead of possible FOR NO KEY UPDATE lock in an UPSERT statement lights go out 00:14
Re: BUG #16486: Prompted password is ignored when password specified in connection string Bruce Momjian 02:19
Adding partitions to the existing table in PostgreSQL Naveen Kumar 17:04
BUG #16652: SELECT pg_reload_conf(); returning true despite loading config has failed PG Bug reporting form 19:32
Re: BUG #16652: SELECT pg_reload_conf(); returning true despite loading config has failed David G. Johnston 20:02

Oct. 4, 2020

Thread Author Time
BUG #16653: Regression in CTE evaluation PG Bug reporting form 16:18
Re: BUG #16653: Regression in CTE evaluation Bruce Momjian 17:13
Re: BUG #16653: Regression in CTE evaluation Tom Lane 17:36
Re: BUG #16653: Regression in CTE evaluation Cherio 22:19

Oct. 5, 2020

Thread Author Time
Re: BUG #16620: Autovacuum does not process certain databases after migration from postgresql 10 Max Vikharev 09:23
BUG #16654: aarch64 can not install postgres12 because of file not exist PG Bug reporting form 10:51
BUG #16655: pg_dump segfault when excluding postgis table PG Bug reporting form 20:54
Re: BUG #16655: pg_dump segfault when excluding postgis table Tom Lane 22:31

Oct. 6, 2020

Thread Author Time
BUG #16656: Last update to PyGreSQL in Postgres repo drop python 2.7 support PG Bug reporting form 07:48
RE: BUG #16645: pg_upgrade does not mark template1 as a system database Y. NAKAGAWA 09:44
RE: [EXTERNAL] BUG #16655: pg_dump segfault when excluding postgis table Godfrin, Philippe E 12:48
Re: [EXTERNAL] BUG #16655: pg_dump segfault when excluding postgis table Cameron Daniel 13:37
Re: BUG #16645: pg_upgrade does not mark template1 as a system database Tom Lane 13:55
Re: Adding partitions to the existing table in PostgreSQL Stephen Frost 16:17
Re: BUG #16655: pg_dump segfault when excluding postgis table Stephen Frost 16:33
Re: BUG #16655: pg_dump segfault when excluding postgis table Tom Lane 17:01
Re: BUG #16655: pg_dump segfault when excluding postgis table 📎 Tom Lane 19:06
Re: BUG #16655: pg_dump segfault when excluding postgis table Tom Lane 21:26
BUG #16657: Index not reflecting update when date to timestamp comparison operation used in index scan PG Bug reporting form 22:22
BUG #16658: HSTORE typecast exception is XX000 - inconsistent with the other cast exceptions (22xxx) PG Bug reporting form 23:45

Oct. 7, 2020

Thread Author Time
Re: BUG #16655: pg_dump segfault when excluding postgis table Tom Lane 01:04
Re: BUG #16657: Index not reflecting update when date to timestamp comparison operation used in index scan Tom Lane 01:31
Re: BUG #16655: pg_dump segfault when excluding postgis table Stephen Frost 02:08
BUG #16659: postgresql leaks memory or do not limit its usage PG Bug reporting form 12:28
BUG #16660: 64-bit build fails when run on a subst drive PG Bug reporting form 16:08
Re: BUG #16655: pg_dump segfault when excluding postgis table Tom Lane 16:56
Re: BUG #16659: postgresql leaks memory or do not limit its usage Tom Lane 17:06
Re: BUG #15858: could not stat file - over 4GB Emil Iggland 19:13

Oct. 8, 2020

Thread Author Time
WIDTH_BUCKET inconsistency Martin Visser 10:57
BUG #16661: Changing columns after the rule is created leads to an error when the RETURNING is used PG Bug reporting form 12:26
Re: WIDTH_BUCKET inconsistency Tom Lane 15:14
Re: WIDTH_BUCKET inconsistency Tom Lane 15:28
BUG #16662: pgbench: error: client 418 script 0 aborted in command 5 query 0: ERROR: invalid page in block 4830 PG Bug reporting form 15:49
Re: BUG #16661: Changing columns after the rule is created leads to an error when the RETURNING is used Tom Lane 17:30

Oct. 9, 2020

Thread Author Time
Re: BUG #16662: pgbench: error: client 418 script 0 aborted in command 5 query 0: ERROR: invalid page in block 4830 Michael Paquier 00:32
Re: BUG #16662: pgbench: error: client 418 script 0 aborted in command 5 query 0: ERROR: invalid page in block 4830 两个孩子的爹 01:53
BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted PG Bug reporting form 13:24
BUG #16664: Problem running django PG Bug reporting form 16:51
Re: BUG #16664: Problem running django David G. Johnston 17:04
Re: BUG #16664: Problem running django Francisco Olarte 17:05
Re: BUG #15858: could not stat file - over 4GB Tom Lane 20:22

Oct. 10, 2020

Thread Author Time
BUG #16665: Segmentation fault PG Bug reporting form 02:38
Re: BUG #16665: Segmentation fault Pavel Stehule 09:04
Re: BUG #16665: Segmentation fault Raphael Megzari 11:19
Re: BUG #16665: Segmentation fault Pavel Stehule 11:23
Re: BUG #16665: Segmentation fault Pavel Stehule 11:25
Re: BUG #16665: Segmentation fault Raphael Megzari 11:27
Re: BUG #15858: could not stat file - over 4GB 📎 Juan José Santamaría Flecha 11:31
Re: BUG #16665: Segmentation fault Pavel Stehule 11:55
Re: BUG #15858: could not stat file - over 4GB Michael Paquier 12:23
Re: BUG #15858: could not stat file - over 4GB Juan José Santamaría Flecha 14:29
Re: BUG #16665: Segmentation fault Raphael Megzari 14:50
Re: BUG #16665: Segmentation fault Pavel Stehule 14:56
Re: BUG #15858: could not stat file - over 4GB Tom Lane 17:42
Re: BUG #15858: could not stat file - over 4GB Juan José Santamaría Flecha 19:00
Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop 📎 Alvaro Herrera 19:06

Oct. 11, 2020

Thread Author Time
Re: BUG #15858: could not stat file - over 4GB Michael Paquier 00:24
Re: BUG #15858: could not stat file - over 4GB Tom Lane 00:34
Re: BUG #16665: Segmentation fault Raphael Megzari 01:13
Re: BUG #16665: Segmentation fault Pavel Stehule 05:36
Re: BUG #16665: Segmentation fault Raphael Megzari 06:54
Re: BUG #16665: Segmentation fault Pavel Stehule 07:13

Oct. 12, 2020

Thread Author Time
Re: BUG #15858: could not stat file - over 4GB Michael Paquier 01:01
Re: BUG #15858: could not stat file - over 4GB Tom Lane 03:27
Identity column behavior discrepancies when inserting one or many rows Jean Prulière 10:05
Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 📎 Pavel Borisov 12:30
Re: BUG #15858: could not stat file - over 4GB Juan José Santamaría Flecha 12:33
BUG #16666: Slight memory leak when running pg_ctl reload PG Bug reporting form 13:32
BUG #16667: COMMIT AND CHAIN does not udpates database metrics ie. xact_commit PG Bug reporting form 13:55
Re: BUG #16666: Slight memory leak when running pg_ctl reload Bruce Momjian 14:19
Re: BUG #16666: Slight memory leak when running pg_ctl reload Tom Lane 14:42
Re: BUG #15858: could not stat file - over 4GB Tom Lane 15:13
Re: BUG #16667: COMMIT AND CHAIN does not udpates database metrics ie. xact_commit Tom Lane 15:21
Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering Pavel Borisov 16:03
Re: Identity column behavior discrepancies when inserting one or many rows David G. Johnston 16:10
Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop Petr Jelinek 16:20
Re: BUG #16666: Slight memory leak when running pg_ctl reload Tom Lane 17:37
Re: Identity column behavior discrepancies when inserting one or many rows Tom Lane 18:12
Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering Tom Lane 20:03
Re: BUG #16667: COMMIT AND CHAIN does not udpates database metrics ie. xact_commit adam grech 21:23
Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering Tom Lane 22:16

Oct. 13, 2020

Thread Author Time
Wrong results from function that selects from vier after "created or replace" Bryn Llewellyn 00:01
Re: BUG #15858: could not stat file - over 4GB Michael Paquier 00:25
Re: Wrong results from function that selects from vier after "created or replace" Tom Lane 00:38
Re: Wrong results from function that selects from vier after "created or replace" David G. Johnston 00:38
Re: Wrong results from function that selects from vier after "created or replace" Bryn Llewellyn 01:15
Re: Wrong results from function that selects from vier after "created or replace" Bryn Llewellyn 01:26
Re: Wrong results from function that selects from vier after "created or replace" David G. Johnston 01:35
Re: Wrong results from function that selects from vier after "created or replace" Christophe Pettus 01:36
Re: Wrong results from function that selects from vier after "created or replace" Tom Lane 01:46
Re: Wrong results from function that selects from vier after "created or replace" David G. Johnston 01:46
Re: Wrong results from function that selects from vier after "created or replace" Tom Lane 01:58
Re: Wrong results from function that selects from vier after "created or replace" Bryn Llewellyn 02:31
Re: Wrong results from function that selects from vier after "created or replace" Bryn Llewellyn 02:57
Re: Wrong results from function that selects from vier after "created or replace" David G. Johnston 03:23
Re: Wrong results from function that selects from vier after "created or replace" Tom Lane 03:28
Re: BUG #16665: Segmentation fault Raphael Megzari 03:31
Re: BUG #16665: Segmentation fault Pavel Stehule 03:38
Re: BUG #16665: Segmentation fault Raphael Megzari 04:07
Re: BUG #16665: Segmentation fault Thomas Munro 04:37
Re: Wrong results from function that selects from vier after "created or replace" Bryn Llewellyn 06:15
Re: BUG #16665: Segmentation fault Pavel Stehule 07:10
BUG #16668: libgeotiff16 missing in PostgreSQL-Common PG Bug reporting form 08:39
Re: BUG #16668: libgeotiff16 missing in PostgreSQL-Common Patrik Uytterhoeven 09:16
Checksum verification fails with StackBuilder when downloading pgAgent Zharas Aitmambet 10:08
Re: BUG #16665: Segmentation fault Tom Lane 14:29

Oct. 14, 2020

Thread Author Time
Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop 📎 Alvaro Herrera 01:12
Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted Kyotaro Horiguchi 03:05
Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted Andres Freund 04:35
Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop Petr Jelinek 05:04
Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted denis.patron 06:47
BUG #16669: cant install postgresql13-server to rhel 6 PG Bug reporting form 07:14
BUG #16670: pgstattuple ERROR: relation "sql_implementation_info" does not exist PG Bug reporting form 12:58
Re: BUG #16670: pgstattuple ERROR: relation "sql_implementation_info" does not exist Tom Lane 14:38
Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted Thomas Munro 19:08
Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted Tom Lane 19:14
BUG #16671: "generated always as" is ignored when updating table through view PG Bug reporting form 20:30
Re: BUG #16671: "generated always as" is ignored when updating table through view Tom Lane 21:49
Re: BUG #16671: "generated always as" is ignored when updating table through view Tom Lane 22:45
BUG #16672: Postgres user passwords are corrupted during migration PG Bug reporting form 23:05

Oct. 15, 2020

Thread Author Time
Re: BUG #16672: Postgres user passwords are corrupted during migration Tom Lane 00:09
RE: BUG #16672: Postgres user passwords are corrupted during migration akada shigeki 00:48
Re: BUG #16672: Postgres user passwords are corrupted during migration Tom Lane 01:07
Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted 📎 Thomas Munro 01:26
Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted Kyotaro Horiguchi 01:42
Re: Checksum verification fails with StackBuilder when downloading pgAgent Sandeep Thakkar 02:37
Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted denni.pat 06:57
BUG #16673: Stack depth limit exceeded error while running sysbench TPC-C PG Bug reporting form 12:43
Re: BUG #16673: Stack depth limit exceeded error while running sysbench TPC-C Tom Lane 14:09
Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop Alvaro Herrera 14:50
Re: Bugreport | Logical replication PostgreSQL 12 | Error after disable / enable replication Alvaro Herrera 15:15
Re: BUG #16577: Segfault on altering a table located in a dropped tablespace Alvaro Herrera 15:19
Re: BUG #16672: Postgres user passwords are corrupted during migration Bruce Momjian 16:46
Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted Thomas Munro 23:54

Oct. 16, 2020

Thread Author Time
BUG #16674: The idle connection get created automatically PG Bug reporting form 09:56
BUG #16675: VALUES not working for CITEXT PG Bug reporting form 10:10
Re: BUG #16675: VALUES not working for CITEXT Pavel Stehule 11:20
Re: BUG #16674: The idle connection get created automatically David G. Johnston 14:23
BUG #16676: SELECT ... FETCH FIRST ROW WITH TIES FOR UPDATE SKIP LOCKED locks rows it doesn't return PG Bug reporting form 19:05
copy command bug Mary LaClair 19:16
Re: copy command bug Tom Lane 19:38
BUG #16677: pgcrypto.pgp_key_id() thinks that a PGP message containing multiple packets is a full keyring. PG Bug reporting form 23:52

Oct. 17, 2020

Thread Author Time
Re: BUG #16677: pgcrypto.pgp_key_id() thinks that a PGP message containing multiple packets is a full keyring. Charles Heywood 00:17
PostgresSQL 10 | Driver 42.2.5 | Float Conversion Issue Thangavel, Parameswaran 01:08
Re: PostgresSQL 10 | Driver 42.2.5 | Float Conversion Issue David G. Johnston 01:32
date/time special values incorrectly cached as constant in plpgsql Tijs van Dam 10:09
Re: date/time special values incorrectly cached as constant in plpgsql David G. Johnston 15:35
Re: date/time special values incorrectly cached as constant in plpgsql Tom Lane 16:18
Re: date/time special values incorrectly cached as constant in plpgsql Tom Lane 20:05
Re: BUG #16604: pg_dump with --jobs breaks SSL connections 📎 Tom Lane 22:58

Oct. 18, 2020

Thread Author Time
Re: BUG #16659: postgresql leaks memory or do not limit its usage 📎 Alexander Zubkov 11:01
Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 19:47
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 19:49
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines Tom Lane 20:00
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 20:01
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 20:03
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 20:08
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines Tom Lane 20:18
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 20:21
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 20:49
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 20:49
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 21:18
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 21:25
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 21:37

Oct. 19, 2020

Thread Author Time
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines 📎 Tom Lane 00:00
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines Tom Lane 00:18
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines pinker 01:02
Re: BUG #16674: The idle connection get created automatically Sathish R 05:37
Re: BUG #16674: The idle connection get created automatically David G. Johnston 06:30
Re: BUG #16674: The idle connection get created automatically David G. Johnston 06:34
Re: BUG #16674: The idle connection get created automatically Sathish R 06:38
Re: BUG #16673: Stack depth limit exceeded error while running sysbench TPC-C David Geier 08:43
Re: BUG #16673: Stack depth limit exceeded error while running sysbench TPC-C Tom Lane 14:31
BUG #16678: The ecpg connect/test5 test sometimes fails on Windows PG Bug reporting form 17:00
Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines Tom Lane 18:47
Re: BUG #16678: The ecpg connect/test5 test sometimes fails on Windows Tom Lane 19:18
Re: invalid alloc size error possible in shm_mq Robert Haas 19:31
Re: BUG #16676: SELECT ... FETCH FIRST ROW WITH TIES FOR UPDATE SKIP LOCKED locks rows it doesn't return David Christensen 22:02
Re: BUG #16676: SELECT ... FETCH FIRST ROW WITH TIES FOR UPDATE SKIP LOCKED locks rows it doesn't return Tom Lane 23:07
Re: BUG #16676: SELECT ... FETCH FIRST ROW WITH TIES FOR UPDATE SKIP LOCKED locks rows it doesn't return David Christensen 23:59

Oct. 20, 2020

Thread Author Time
Re: BUG #16676: SELECT ... FETCH FIRST ROW WITH TIES FOR UPDATE SKIP LOCKED locks rows it doesn't return David Christensen 00:33
Re: invalid alloc size error possible in shm_mq Michael Paquier 01:52
BUG #16679: Incorrect encoding of database name PG Bug reporting form 10:44

Browse Archives

Prev | Next
Jump to day: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31