Mailing lists [pgsql-bugs]

1 October 2019

• 00:48   RE: BUG #16031: Group by returns duplicate groups David Raymond
• 02:34   Re: BUG #16031: Group by returns duplicate groups Peter Geoghegan
• 08:40   Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
• 15:54   psql: FATAL: database “” does not exist Naima Shaikh
• 17:55   RE: BUG #16031: Group by returns duplicate groups David Raymond
• 18:21   Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
• 18:22   RE: BUG #16031: Group by returns duplicate groups David Raymond
• 18:26   Re: psql: FATAL: database “” does not exist David G. Johnston
• 18:28   Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
• 19:06   BUG #16032: pg_basebackup when running on Windows doesn't clean up on failure correctly PG Bug reporting form
• 19:25   RE: BUG #16031: Group by returns duplicate groups David Raymond
• 21:34   RE: BUG #16031: Group by returns duplicate groups David Raymond
• 22:26   Re: BUG #16031: Group by returns duplicate groups Andrew Gierth

2 October 2019

• 15:04   BUG #16033: segmentation fault when runing update PG Bug reporting form
• 16:51   Re: BUG #16033: segmentation fault when runing update Tom Lane
• 18:40   Re: BUG #16033: segmentation fault when runing update Miha Vrhovnik
• 18:47   BUG #16034: `\set ECHO all` doesn't work for \e command PG Bug reporting form
• 18:56   Re: BUG #16034: `\set ECHO all` doesn't work for \e command Tom Lane
• 19:11   Re: BUG #16034: `\set ECHO all` doesn't work for \e command Pavlo Golub
• 19:15   Re: BUG #16033: segmentation fault when runing update Tom Lane
• 19:51   Re: BUG #16034: `\set ECHO all` doesn't work for \e command Tom Lane
• 20:47   Re: BUG #16034: `\set ECHO all` doesn't work for \e command Daniel Verite
• 21:36   RE: BUG #16031: Group by returns duplicate groups David Raymond

3 October 2019

• 09:38   BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql PG Bug reporting form
• 17:08   Re: BUG #16034: `\set ECHO all` doesn't work for \e command Pavlo Golub
• 17:51   Re: BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql Tom Lane
• 18:33   Write skew anmalies are found in SERIALIZABLE isolation 张舒燕
• 20:46   Re: BUG #16034: `\set ECHO all` doesn't work for \e command Daniel Verite
• 22:59   Re: BUG #16034: `\set ECHO all` doesn't work for \e command Tom Lane

4 October 2019

• 00:05   Re: Write skew anmalies are found in SERIALIZABLE isolation Peter Geoghegan
• 03:29   BUG #16036: Segmentation fault while doing an update PG Bug reporting form
• 03:55   Re: BUG #16036: Segmentation fault while doing an update Антон Власов
• 04:09   Re: BUG #16036: Segmentation fault while doing an update Andres Freund
• 04:14   Re: BUG #16036: Segmentation fault while doing an update Антон Власов
• 04:20   Re: BUG #16036: Segmentation fault while doing an update Andres Freund
• 04:24   Re: BUG #16036: Segmentation fault while doing an update Антон Власов
• 04:26   Re: BUG #16036: Segmentation fault while doing an update Антон Власов
• 04:36   Re: Write skew anmalies are found in SERIALIZABLE isolation 张舒燕
• 04:45   Re: BUG #16036: Segmentation fault while doing an update Антон Власов
• 04:52   Re: BUG #16036: Segmentation fault while doing an update Антон Власов
• 05:11   Re: BUG #16036: Segmentation fault while doing an update Антон Власов
• 06:20   Re: BUG #16036: Segmentation fault while doing an update Andres Freund
• 06:26   Re: BUG #16036: Segmentation fault while doing an update Tom Lane
• 06:36   Re: BUG #16036: Segmentation fault while doing an update Andres Freund
• 06:42   Re: BUG #16036: Segmentation fault while doing an update Tom Lane
• 07:30   Re: BUG #16036: Segmentation fault while doing an update Andres Freund
• 08:00   BUG #16037: Assertion fails in varbit_out PG Bug reporting form
• 08:34   Re: BUG #16037: Assertion fails in varbit_out Tom Lane
• 08:42   Re: BUG #16037: Assertion fails in varbit_out Andres Freund
• 08:52   Re: BUG #16037: Assertion fails in varbit_out Tom Lane
• 10:28   Re: Write skew anmalies are found in SERIALIZABLE isolation Konstantin Knizhnik
• 11:10   Re: BUG #16035: STATEMENT_TIMEOUT not working when we have singlequote usage inside CTE which is used in inner sql Tatsuo Ishii
• 13:01   Bugs in google search for Postgres database Satish Kumar
• 14:13   Re: Bugs in google search for Postgres database Jaime Soler
• 16:29   BUG #16038: Alter table - SegFault PG Bug reporting form
• 17:12   Re: [BUGS] bug or simply not enough stack space? Merlin Moncure
• 17:43   Re: BUG #16038: Alter table - SegFault Alvaro Herrera
• 18:26   Re: BUG #16038: Alter table - SegFault Andres Freund
• 19:06   Re: [BUGS] bug or simply not enough stack space? Tom Lane
• 22:28   BUG #16039: PANIC when activating replication slots in Postgres 12.0 64bit under Windows PG Bug reporting form
• 22:28   Re: BUG #16036: Segmentation fault while doing an update Andres Freund
• 23:06   Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Andres Freund
• 23:20   BUG #16040: PL/PGSQL RETURN QUERY statement never uses a parallel plan PG Bug reporting form
• 23:49   Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Andres Freund

5 October 2019

• 00:43   Re: BUG #16036: Segmentation fault while doing an update Andres Freund
• 01:24   Re: BUG #16036: Segmentation fault while doing an update Andres Freund
• 01:40   Re: BUG #16036: Segmentation fault while doing an update Peter Geoghegan
• 01:43   BUG #16041: Error shows up both in pgAdmin and in Ruby (pg gem) - Segmentation fault PG Bug reporting form
• 07:45   Re: BUG #16036: Segmentation fault while doing an update Andres Freund
• 10:40   AW: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Hans Buschmann
• 14:06   BUG #16042: incorrect .gitignore file PG Bug reporting form
• 14:33   Reply to the "Write skew anmalies are found in SERIALIZABLE isolation" 张舒燕
• 14:43   Non-null values of recovery functions after promote or crash ofprimary Martín Marqués
• 14:43   Non-null values of recovery functions after promote or crash ofprimary Martín Marqués
• 18:30   Re: BUG #16036: Segmentation fault while doing an update Tom Lane
• 19:26   Re: BUG #16036: Segmentation fault while doing an update Andres Freund
• 19:28   Re: BUG #16042: incorrect .gitignore file Tom Lane
• 19:34   Re: BUG #16042: incorrect .gitignore file Andres Freund
• 19:48   Re: BUG #16042: incorrect .gitignore file Tom Lane

6 October 2019

• 07:55   Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Michael Paquier
• 08:00   Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Michael Paquier
• 10:22   Re: BUG #16035: STATEMENT_TIMEOUT not working when we have singlequote usage inside CTE which is used in inner sql Tatsuo Ishii
• 17:29   Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
• 22:15   [PATCH] Re: BUG #16032: pg_basebackup when running on Windows doesn't clean up on failure correctly Rob Emery

7 October 2019

• 04:21   Re: [PATCH] Re: BUG #16032: pg_basebackup when running on Windowsdoesn't clean up on failure correctly Michael Paquier
• 07:27   Re: BUG #16041: Error shows up both in pgAdmin and in Ruby (pg gem) - Segmentation fault Fahar Abbas
• 14:21   BUG #16043: Duplicate Entry Key Message on postgres PG Bug reporting form
• 16:35   Re: BUG #16043: Duplicate Entry Key Message on postgres Tom Lane
• 16:40   Re: BUG #16043: Duplicate Entry Key Message on postgres Komal Sookee
• 18:52   Re: [PATCH] Re: BUG #16032: pg_basebackup when running on Windows doesn't clean up on failure correctly Rob Emery
• 21:29   RE: BUG #16031: Group by returns duplicate groups David Raymond
• 21:29   Re: BUG #16031: Group by returns duplicate groups Andrew Gierth
• 22:58   Re: BUG #16043: Duplicate Entry Key Message on postgres Tomas Vondra
• 23:53   Re: BUG #16031: Group by returns duplicate groups Tomas Vondra

8 October 2019

• 03:32   Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Michael Paquier
• 13:07   BUG #16044: Could not send data to server PG Bug reporting form
• 15:30   Potential to_date(string, string) function malfunction Pavel Pleva
• 16:36   RE: BUG #16031: Group by returns duplicate groups David Raymond
• 18:38   Re: Potential to_date(string, string) function malfunction Tom Lane
• 19:09   Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Andres Freund
• 19:36   Re: BUG #16044: Could not send data to server David G. Johnston
• 20:08   BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 PG Bug reporting form
• 21:03   Re: Non-null values of recovery functions after promote or crash ofprimary Stephen Frost
• 21:03   Re: Non-null values of recovery functions after promote or crash ofprimary Stephen Frost
• 22:56   Re: Non-null values of recovery functions after promote or crash of primary Martín Marqués
• 22:56   Re: Non-null values of recovery functions after promote or crash of primary Martín Marqués

9 October 2019

• 04:49   Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` settingshould be documented Bruce Momjian
• 07:42   Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Michael Paquier
• 12:22   BUG #16046: xpath returns CDATA tag along with the value in postgres 12 PG Bug reporting form
• 16:24   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 16:59   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 17:07   Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
• 17:18   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 17:22   Re: Potential to_date(string, string) function malfunction Pavel Pleva
• 17:28   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 17:50   AW: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Hans Buschmann
• 18:20   Re: AW: install error Scott Laing

10 October 2019

• 02:07   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 02:18   Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
• 02:28   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 02:41   Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
• 04:48   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Andres Freund
• 08:21   Re: BUG #16038: Alter table - SegFault Andres Freund
• 08:28   BUG #16047: please help my postgress page can't be uploaded perfectly PG Bug reporting form
• 08:32   please help, my postgress page can't be uploaded perfectly Fafa Fahri
• 16:43   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 17:19   Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
• 18:25   Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Andres Freund
• 19:33   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 20:04   Re: please help, my postgress page can't be uploaded perfectly David G. Johnston
• 23:14   Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
• 23:40   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra

11 October 2019

• 03:28   Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows Michael Paquier
• 17:03   BUG #16048: SQLSTATE 22P05 is not captured in exception clause PG Bug reporting form
• 17:12   BUG #16049: log_line_prefix=%a and log_connections - application_name missing PG Bug reporting form
• 17:19   Re: BUG #16048: SQLSTATE 22P05 is not captured in exception clause Tom Lane
• 17:36   Re: BUG #16049: log_line_prefix=%a and log_connections - application_name missing Tom Lane
• 18:05   BUG #16050: Server crash on CREATE TEXT SEARCH DICTIONARY with a wrong AffFile PG Bug reporting form
• 20:27   Re: BUG #16050: Server crash on CREATE TEXT SEARCH DICTIONARY with awrong AffFile Tomas Vondra
• 21:35   Re: BUG #16050: Server crash on CREATE TEXT SEARCH DICTIONARY with awrong AffFile Tomas Vondra

12 October 2019

• 01:42   BUG #16051: PQgetvalue(res,0,0) is null, PQgetlength(res,0,0) is 10 PG Bug reporting form
• 06:30   Re: BUG #16051: PQgetvalue(res,0,0) is null, PQgetlength(res,0,0) is 10 Tom Lane
• 11:42   Re: BUG #16051: PQgetvalue(res,0,0) is null, PQgetlength(res,0,0) is 10 Bart Smink
• 17:17   Re: BUG #16051: PQgetvalue(res,0,0) is null, PQgetlength(res,0,0) is 10 Andrew Gierth
• 17:17   Re: BUG #16051: PQgetvalue(res,0,0) is null, PQgetlength(res,0,0) is 10 Tom Lane
• 17:58   BUG #16052: pg_dump --no-comments not working PG Bug reporting form
• 18:10   Re: BUG #16052: pg_dump --no-comments not working Tom Lane
• 19:26   BUG #16053: Query planner performance regression in sql query with multiple CTE in v12 PG Bug reporting form
• 20:17   Re: BUG #16053: Query planner performance regression in sql query with multiple CTE in v12 Andrew Gierth

13 October 2019

• 03:10   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 20:44   ERROR: invalid input syntax for integer: "0A000" McLaughlin, Michael
• 21:26   Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
• 21:31   Re: ERROR: invalid input syntax for integer: "0A000" Tom Lane
• 22:23   Re: ERROR: invalid input syntax for integer: "0A000" Tomas Vondra
• 23:38   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra

14 October 2019

• 05:24   BUG #16054: Slowest individual queries PG Bug reporting form
• 14:24   Re: BUG #16054: Slowest individual queries Tomas Vondra
• 16:08   BUG #16055: pgAdmin 4 - ERROR: operator does not exist: - oid PG Bug reporting form
• 17:16   Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
• 18:19   BUG #16056: Actually PGADMIN4 PG Bug reporting form
• 19:35   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 22:53   Re: BUG #16056: Actually PGADMIN4 David G. Johnston

15 October 2019

• 02:30   Re: BUG #16055: pgAdmin 4 - ERROR: operator does not exist: - oid Tom Lane
• 03:18   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 03:35   Re: BUG #16054: Slowest individual queries Jeff Janes
• 07:41   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Justin Pryzby
• 10:07   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 10:51   BUG #16057: Faulty PK violation PG Bug reporting form
• 11:26   BUG #16058: show session_user shows a not clear error message PG Bug reporting form
• 15:34   Re: BUG #16049: log_line_prefix=%a and log_connections -application_name missing death lock
• 16:11   BUG #16059: Tab-completion of filenames in COPY commands removes required quotes PG Bug reporting form
• 16:38   Re: BUG #16059: Tab-completion of filenames in COPY commands removesrequired quotes Francisco Olarte
• 16:52   RE: BUG #16059: Tab-completion of filenames in COPY commandsremoves required quotes Steven Winfield
• 21:52   BUG #16060: JDBC - badly gets DateOffsetTime value from database PG Bug reporting form

16 October 2019

• 00:11   Duplicate Workers entries in some EXPLAIN plans Maciek Sakrejda
• 07:20   Re: BUG #16060: JDBC - badly gets DateOffsetTime value from database Michael Paquier
• 07:41   Re: BUG #16058: show session_user shows a not clear error message Michael Paquier
• 08:35   Re: BUG #16060: JDBC - badly gets DateOffsetTime value from database Dave Cramer
• 09:10   Re: ERROR: multixact X from before cutoff Y found to be still running Thomas Munro
• 09:10   Re: ERROR: multixact X from before cutoff Y found to be still running Thomas Munro
• 09:57   Re: Re: BUG #15929: logical decoding can not write down the analyse result when the output file is touched. movead.li@highgo.ca
• 10:16   Re: Duplicate Workers entries in some EXPLAIN plans Tom Lane
• 11:24   Re: Duplicate Workers entries in some EXPLAIN plans Maciek Sakrejda
• 11:50   BUG #16061: pgadmin PG Bug reporting form
• 13:52   Re: BUG #16060: JDBC - badly gets DateOffsetTime value from database stan@marencik.cz
• 14:33   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 14:42   Re: BUG #16049: log_line_prefix=%a and log_connections -application_name missing death lock
• 15:27   Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
• 16:26   Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
• 16:41   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 17:33   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
• 19:01   pg_restore creates duplicate records when used with --roleparameter Ivan Pantić
• 20:09   Re: ERROR: multixact X from before cutoff Y found to be still running Bossart, Nathan
• 20:09   Re: ERROR: multixact X from before cutoff Y found to be still running Bossart, Nathan
• 20:11   Re: ERROR: multixact X from before cutoff Y found to be still running Jeremy Schneider
• 20:11   Re: ERROR: multixact X from before cutoff Y found to be still running Jeremy Schneider

17 October 2019

• 02:25   Re: ERROR: multixact X from before cutoff Y found to be still running Thomas Munro
• 02:25   Re: ERROR: multixact X from before cutoff Y found to be still running Thomas Munro
• 04:07   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
• 04:31   Re: BUG #16026: default_tablespace in postgresql.conf is used insteadof the database's default. Thomas Munro
• 08:40   Re: BUG #16049: log_line_prefix=%a and log_connections -application_name missing Michael Paquier
• 10:12   BUG #16062: pg_restore using ssl certs PG Bug reporting form
• 10:59   BUG #16063: Error retrieving data from the server: INTERNAL SERVER ERROR: string indices must be integers PG Bug reporting form
• 11:17   Re: BUG #16062: pg_restore using ssl certs Ashutosh Sharma
• 12:23   RE: BUG #16026: default_tablespace in postgresql.conf is used insteadof the database's default. Crevon Virgile
• 17:40   Re: BUG #16063: Error retrieving data from the server: INTERNALSERVER ERROR: string indices must be integers David G. Johnston
• 20:58   BUG #16064: Ldap Authentication failing with pg_hba.conf entry PG Bug reporting form
• 22:08   postgres has no spinlock support on riscv rv64imafdc Robert Henry

18 October 2019

• 00:54   Re: BUG #16064: Ldap Authentication failing with pg_hba.conf entry Stephen Frost
• 02:16   Re: BUG #16064: Ldap Authentication failing with pg_hba.conf entry Jeff Janes
• 03:34   Re: BUG #16064: Ldap Authentication failing with pg_hba.conf entry Yudhveer Kandukuri
• 05:07   checkpoint process is hang 石勇虎
• 05:27   Checking types for arguments Gavin M2301
• 06:34   Fwd: Checking types for arguments Gavin M2301
• 10:00   Re: postgres has no spinlock support on riscv rv64imafdc Tom Lane
• 12:13   Re: pg_restore creates duplicate records when used with --role parameter Tom Lane
• 13:14   Re: BUG #16029: pg_basebackup - At least one WAL file is missing Georg H.
• 14:17   Re: pg_restore creates duplicate records when used with --roleparameter Ivan Pantić
• 14:40   Re: BUG #16026: default_tablespace in postgresql.conf is usedinstead of the database's default. Alvaro Herrera
• 14:40   Re: BUG #16026: default_tablespace in postgresql.conf is usedinstead of the database's default. Alvaro Herrera
• 18:01   BUG #16065: The operation nodes in query plans outputted by EXPLAIN have no authoritative definitions. PG Bug reporting form
• 22:47   BUG #16066: Ldap Authentication failure on PostgreSQL 10.10 PG Bug reporting form

19 October 2019

• 02:12   Re: BUG #16066: Ldap Authentication failure on PostgreSQL 10.10 Stephen Frost
• 13:22   Re: postgres has no spinlock support on riscv rv64imafdc Andres Freund
• 17:54   BUG #16067: Failed system call was semget PG Bug reporting form
• 22:08   BUG #16068: Collate of 'Norwegian Bokmål' is problematic PG Bug reporting form
• 22:33   Re: BUG #16067: Failed system call was semget Tomas Vondra
• 23:03   Re: BUG #16068: Collate of 'Norwegian Bokmål' is problematic Tom Lane
• 23:49   BUG #16069: Error installing yum.rpm PG Bug reporting form

20 October 2019

• 00:07   Re: BUG #16065: The operation nodes in query plans outputted byEXPLAIN have no authoritative definitions. Jeff Janes
• 06:42   Re: BUG #16067: Failed system call was semget Tom Lane
• 06:51   Re: BUG #16065: The operation nodes in query plans outputted byEXPLAIN have no authoritative definitions. Eric Toombs
• 07:23   Re: postgres has no spinlock support on riscv rv64imafdc Tom Lane
• 11:58   BUG #16070: A double-free bug in interfaces/libpq/fe-secure-openssl.c PG Bug reporting form
• 17:17   Re: BUG #16070: A double-free bug in interfaces/libpq/fe-secure-openssl.c Tom Lane

21 October 2019

• 00:57   Re: Re: BUG #16068: Collate of 'Norwegian Bokmål' is problematic Tom Lane
• 06:25   Re: BUG #16070: A double-free bug ininterfaces/libpq/fe-secure-openssl.c Michael Paquier
• 06:44   Re: BUG #16070: A double-free bug in interfaces/libpq/fe-secure-openssl.c Tom Lane
• 08:02   Re: BUG #16035: STATEMENT_TIMEOUT not working when we have singlequote usage inside CTE which is used in inner sql Tatsuo Ishii
• 08:03   Re: BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql Tom Lane
• 09:33   BUG #16071: Server crashes when 'numeric' data type is used on any plpython Function PG Bug reporting form
• 11:54   Re: Re: BUG #16068: Collate of 'Norwegian Bokmål' is problematic Robert Ford
• 13:22   PGDG strech : postgresql-11-postgis-2.5 won't install beacause ofmissing dependency Bruno DUPUIS
• 14:29   Incorrect rounding of double values at max precision Gilleain Torrance
• 17:20   Re: Re: Re: BUG #16068: Collate of 'Norwegian Bokmål' is problematic Tom Lane
• 18:00   Re: BUG #16071: Server crashes when 'numeric' data type is used on any plpython Function Tom Lane
• 22:42   Re: Incorrect rounding of double values at max precision Tom Lane

22 October 2019

• 01:26   Re: Incorrect rounding of double values at max precision Andrew Gierth
• 02:02   Re: BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql Tom Lane
• 05:41   Re: Incorrect rounding of double values at max precision Tom Lane
• 06:53   Re: Incorrect rounding of double values at max precision Andrew Gierth
• 08:29   Re: Duplicate Workers entries in some EXPLAIN plans Maciek Sakrejda
• 08:34   Re: Duplicate Workers entries in some EXPLAIN plans Tom Lane
• 12:25   RE: Incorrect rounding of double values at max precision Gilleain Torrance
• 13:02   RE: PGDG strech : postgresql-11-postgis-2.5 won't install beacause ofmissing dependency Bruno DUPUIS
• 21:54   Re: Incorrect rounding of double values at max precision Andrew Gierth

23 October 2019

• 04:24   CSV file t psotgresql table m krishna
• 09:29   BUG #16072: Two transaction to delete all data, The result is not hopeful PG Bug reporting form
• 09:39   Re: BUG #16072: Two transaction to delete all data, The result is not hopeful Guillaume Lelarge
• 14:46   memory problems and crash of db when deleting data from table withthousands of partitions Josef Machytka
• 15:13   BUG #16073: pg_dump build crashes half way PG Bug reporting form
• 15:47   Re: memory problems and crash of db when deleting data from tablewith thousands of partitions Tomas Vondra

24 October 2019

• 01:08   Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Bruce Momjian
• 01:42   BUG #16074: Consistently link latest repo RPM release to pgdg-redhat-repo-latest PG Bug reporting form
• 10:25   BUG #16075: The favicon of https://www.postgresql.org is vague on MacBook Pro with retina display PG Bug reporting form
• 12:59   Re: ERROR: subtransaction logged without previous top-level txn record Arseny Sher
• 14:06   PostgreSQL 12 installation fails because locale name contained non-english characters Skjalg A. Skagen
• 18:12   BUG #16076: JIT causes huge delays in a complex query. jit=off solves it. PG Bug reporting form
• 19:09   BUG #16077: Sorting of table list depends on platform PG Bug reporting form
• 20:01   Re: BUG #16077: Sorting of table list depends on platform Tom Lane
• 21:19   Re: BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql Tom Lane
• 21:37   Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented Tom Lane
• 21:37   Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented Tom Lane

25 October 2019

• 00:17   Re: BUG #16073: pg_dump build crashes half way Andres Freund
• 00:31   Re: ERROR: subtransaction logged without previous top-level txnrecord Andres Freund
• 00:38   Re: BUG #16046: xpath returns CDATA tag along with the value in postgres 12 Tom Lane
• 02:14   Re: BUG #16046: xpath returns CDATA tag along with the value inpostgres 12 Chapman Flack
• 02:34   Re: BUG #16046: xpath returns CDATA tag along with the value inpostgres 12 Chapman Flack
• 04:04   Re: BUG #16076: JIT causes huge delays in a complex query. jit=offsolves it. Andres Freund
• 04:45   Re: BUG #16046: xpath returns CDATA tag along with the value inpostgres 12 Chapman Flack
• 04:58   Re: BUG #16076: JIT causes huge delays in a complex query. jit=offsolves it. Yuri Astrakhan
• 09:56   Re: ERROR: subtransaction logged without previous top-level txn record Arseny Sher
• 11:01   BUG #16078: Problems starting and running the app stack builder PG Bug reporting form
• 20:16   Re: BUG #16046: xpath returns CDATA tag along with the value inpostgres 12 Markus Winand
• 20:27   Re: BUG #16046: xpath returns CDATA tag along with the value in postgres 12 Tom Lane

26 October 2019

• 02:16   BUG #16079: Question Regarding the BUG #16064 PG Bug reporting form
• 04:48   Re: BUG #16067: Failed system call was semget Thomas Munro
• 07:30   BUG #16080: pg_ctl is failed if a fake cmd.exe exist in the current directory. PG Bug reporting form
• 07:32   BUG #16081: pg_upgrade is failed if a fake cmd.exe exist in the current directory. PG Bug reporting form
• 10:46   BUG #16082: TOAST's pglz_decompress access to uninitialized data, if the database is corrupted. PG Bug reporting form
• 16:36   Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in the current directory. Tom Lane
• 17:15   Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in thecurrent directory. Juan José Santamaría Flecha
• 18:20   Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in the current directory. Tom Lane
• 20:33   Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in thecurrent directory. Juan José Santamaría Flecha
• 20:44   Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in the current directory. Tom Lane

27 October 2019

• 00:56   Re: BUG #16082: TOAST's pglz_decompress access to uninitializeddata, if the database is corrupted. Tomas Vondra
• 13:07   Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in thecurrent directory. Juan José Santamaría Flecha
• 18:42   Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in the current directory. Tom Lane
• 23:55   Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in thecurrent directory. Juan José Santamaría Flecha

28 October 2019

• 10:15   BUG #16083: Different Result PG Bug reporting form
• 10:35   Re: BUG #16083: Different Result Pavel Stehule
• 17:28   RE: BUG #15858: could not stat file - over 4GB william allen
• 17:28   RE: BUG #15858: could not stat file - over 4GB william allen
• 18:18   Re: memory problems and crash of db when deleting data from tablewith thousands of partitions Josef Machytka
• 18:47   Re: BUG #16079: Question Regarding the BUG #16064 Stephen Frost
• 19:24   Re: memory problems and crash of db when deleting data from tablewith thousands of partitions Tomas Vondra
• 20:13   Re: BUG #15858: could not stat file - over 4GB Juan José Santamaría Flecha
• 20:13   Re: BUG #15858: could not stat file - over 4GB Juan José Santamaría Flecha
• 21:16   Re: BUG #16080: pg_ctl is failed if a fake cmd.exe exist in the current directory. Tom Lane

29 October 2019

• 03:19   BUG #16084: Server couldn't be contacted PG Bug reporting form
• 10:12   BUG #16085: Potential missing version information available for /usr/pgsql-12/lib/libpq.so.5 PG Bug reporting form
• 11:14   Backup/restore problem Pavel Popov
• 13:25   BUG #16086: Cannot connect using psql, however I can connect using pgadmin PG Bug reporting form
• 14:14   Re: BUG #16086: Cannot connect using psql, however I can connect using pgadmin Sergei Kornilov
• 14:23   Re: BUG #16084: Server couldn't be contacted Ashutosh Sharma
• 14:27   Re: BUG #16086: Cannot connect using psql, however I can connectusing pgadmin Jeff Janes
• 14:51   Re: BUG #16086: Cannot connect using psql, however I can connectusing pgadmin Ashutosh Sharma
• 14:54   Re: BUG #16086: Cannot connect using psql, however I can connectusing pgadmin Muziwandile Zwane
• 17:39   Re: Backup/restore problem Tom Lane
• 18:16   BUG #16087: Segmentation fault on ALTER TABLE PG Bug reporting form
• 18:26   Re: BUG #16087: Segmentation fault on ALTER TABLE Tom Lane
• 18:26   BUG #16088: Multiple foreigh keys created on "ALTER TABLE" command PG Bug reporting form
• 18:37   Re: BUG #16088: Multiple foreigh keys created on "ALTER TABLE" command Tom Lane

30 October 2019

• 02:56   Re: BUG #16086: Cannot connect using psql, however I can connectusing pgadmin Euler Taveira
• 11:15   Re: Backup/restore problem Pavel Popov
• 12:59   Re: BUG #16053: Query planner performance regression in sql querywith multiple CTE in v12 Federico
• 14:36   insert into inet from text automatically adding subnet Jeremy Finzel
• 15:54   BUG #16089: Index only scan does not happen but expected PG Bug reporting form
• 17:05   Re: insert into inet from text automatically adding subnet Tom Lane
• 17:13   Re: BUG #16089: Index only scan does not happen but expected Dmitry Dolgov
• 17:18   RE: BUG #16089: Index only scan does not happen but expected Stepan Yankevych
• 17:35   Re: memory problems and crash of db when deleting data from tablewith thousands of partitions Josef Machytka
• 17:46   BUG #16090: Migración con pg_dump PG Bug reporting form
• 18:10   Re: BUG #16089: Index only scan does not happen but expected Dmitry Dolgov
• 18:14   Re: BUG #16089: Index only scan does not happen but expected Dmitry Dolgov
• 18:27   RE: BUG #16089: Index only scan does not happen but expected Stepan Yankevych
• 19:58   BUG #16091: xpath fails to compute "name()", regression PG Bug reporting form
• 21:10   Re: BUG #16091: xpath fails to compute "name()", regression Tom Lane
• 21:16   Re: memory problems and crash of db when deleting data from tablewith thousands of partitions Tomas Vondra
• 23:08   Re: BUG #16091: xpath fails to compute "name()", regression Cherio
• 23:30   Re: BUG #16082: TOAST's pglz_decompress access to uninitializeddata, if the database is corrupted. Alvaro Herrera
• 23:51   Re: BUG #16090: Migración conpg_dump Alvaro Herrera

31 October 2019

• 03:00   Re: BUG #16082: TOAST's pglz_decompress access to uninitializeddata, if the database is corrupted. Tomas Vondra
• 11:12   a error happends when create a table in postgresql10.ubuntu 18.04 ?????
• 17:29   BUG #16092: json[b]_to_recordset and json[b]_populate_record do not read properties with mixed-case names PG Bug reporting form
• 17:41   Re: a error happends when create a table in postgresql10.ubuntu18.04 Tomas Vondra
• 17:41   Re: BUG #16092: json[b]_to_recordset and json[b]_populate_record do not read properties with mixed-case names Sergei Kornilov