Mailing lists [pgsql-bugs]

1 April 2019

• 08:35   Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita
• 09:01   Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita
• 09:23   Re: BUG #15724: Can't create foreign table as partition Amit Langote
• 09:32   BUG #15725: pgAgent not working on Another database other than Postgres PG Bug reporting form
• 09:40   Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita
• 09:45   Re: BUG #15724: Can't create foreign table as partition Amit Langote
• 09:57   Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita
• 14:12   BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker PG Bug reporting form
• 16:29   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Michael Paquier
• 16:49   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker ANASTACIO Tiago
• 21:30   Parallel query execution introduces performance regressions Jinho Jung
• 21:34   Re: Parallel query execution introduces performance regressions Andres Freund
• 21:52   Re: Parallel query execution introduces performance regressions Peter Geoghegan
• 22:00   Re: Parallel query execution introduces performance regressions Andres Freund
• 22:05   Re: Parallel query execution introduces performance regressions Peter Geoghegan
• 22:08   Re: Parallel query execution introduces performance regressions Jinho Jung
• 22:13   Re: Parallel query execution introduces performance regressions Andres Freund

2 April 2019

• 00:59   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
• 03:24   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
• 03:32   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
• 03:41   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Peter Geoghegan
• 06:21   Re: Parallel query execution introduces performance regressions David Rowley
• 12:59   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker ANASTACIO Tiago
• 13:23   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
• 13:30   BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed PG Bug reporting form
• 13:36   BUG #15728: an index that created with keyword ONLY, when add new partition ,should not be auto created PG Bug reporting form
• 18:12   Re: BUG #15728: an index that created with keyword ONLY, when add newpartition ,should not be auto created David G. Johnston
• 18:19   Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Tom Lane
• 18:29   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 18:44   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane
• 18:47   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 18:51   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Alvaro Herrera
• 18:51   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane
• 18:53   BUG #15729: Error 'invalid memory alloc request size' during updating a big xml field PG Bug reporting form
• 19:00   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 19:13   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 20:00   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Alvaro Herrera
• 20:04   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
• 20:10   Re: BUG #15722: 9000x performance regression on query startingPostgreSQL 10 due to bad query plan Jeff Janes
• 20:11   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 20:13   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane
• 20:17   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 20:17   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Alvaro Herrera
• 20:30   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane
• 20:35   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Жарков Роман
• 20:35   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 22:54   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro

3 April 2019

• 06:58   BUG #15730: Using filter function to interpolate data, the length limit of table field is invalid PG Bug reporting form
• 10:38   BUG #15731: CVE-2019-9193 PG Bug reporting form
• 10:42   Re: BUG #15731: CVE-2019-9193 Magnus Hagander
• 10:46   RE: Re: BUG #15731: CVE-2019-9193 Rajwade, Abhijit
• 11:10   Re: Re: BUG #15731: CVE-2019-9193 Magnus Hagander
• 11:29   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
• 11:38   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
• 15:20   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Alvaro Herrera
• 15:59   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
• 16:29   Bug report - incorrect value displayed in jsonb column for large numbers Michał Iwańczuk
• 18:29   BUG #15732: Jessie backports removed from network PG Bug reporting form
• 19:48   Re: Bug report - incorrect value displayed in jsonb column for large numbers Tom Lane
• 20:07   Re: BUG #15383: Join Filter cost estimation problem in 10.5 Tom Lane
• 20:30   Re: Bug report - incorrect value displayed in jsonb column for largenumbers Jerry Sievert
• 21:22   BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails PG Bug reporting form

4 April 2019

• 04:35   Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Michael Paquier
• 07:37   Re: BUG #15383: Join Filter cost estimation problem in 10.5 David Rowley
• 09:16   Re: BUG #15722: 9000x performance regression on query startingPostgreSQL 10 due to bad query plan Jeremy Evans
• 10:54   BUG #15734: Walsender process crashing when executing SHOW ALL; PG Bug reporting form
• 13:31   Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Amit Langote
• 13:48   Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Michael Paquier
• 15:59   BUG #15735: postgis extension missing PG Bug reporting form
• 17:36   Bug trying to view table Rossiter, Russell D.
• 18:08   BUG #15736: running bootstrap script ... FATAL: invalid value for parameter "port": "" PG Bug reporting form
• 20:28   Re: BUG #15735: postgis extension missing bricklen
• 20:42   Re: Bug trying to view table bricklen
• 20:52   Re: BUG #15735: postgis extension missing Prakash Ramakrishnan
• 22:35   Re: BUG #15735: postgis extension missing Tom Lane
• 22:40   Re: BUG #15735: postgis extension missing Prakash Ramakrishnan
• 23:08   BUG #15737: Unexpectedly Deleting full table when referring CTE (With Clause ) data,in a Subquery in another CTE PG Bug reporting form
• 23:26   Re: BUG #15737: Unexpectedly Deleting full table when referring CTE(With Clause ) data,in a Subquery in another CTE David G. Johnston

5 April 2019

• 03:43   Re: BUG #15737: Unexpectedly Deleting full table when referring CTE(With Clause ) data,in a Subquery in another CTE David Rowley
• 06:22   Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Amit Langote
• 08:07   Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Amit Langote
• 09:40   BUG #15738: _SPI_connected fail PG Bug reporting form
• 15:07   Re: BUG #15724: Can't create foreign table as partition Etsuro Fujita

6 April 2019

• 19:23   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane
• 19:28   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 20:09   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
• 20:10   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 20:17   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 20:27   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund

7 April 2019

• 02:10   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 23:33   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund

8 April 2019

• 05:59   BUG #15739: PgAdmin4 4.4 does not work with latest psycopg2 (2.8.1) PG Bug reporting form
• 06:02   Re: BUG #15739: PgAdmin4 4.4 does not work with latest psycopg2 (2.8.1) Rizwan Wangde
• 07:50   Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Michael Paquier
• 07:55   Re: BUG #15733: An insert destined at partition created after acolumn has been dropped from the parent table fails Amit Langote
• 10:21   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Amit Langote
• 10:39   Re: BUG #15734: Walsender process crashing when executing SHOW ALL; Michael Paquier
• 11:18   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Amit Langote
• 13:23   PostgreSQL 9.5 service stopped intermittently on windows 10 Proversion 1703. Kadam, Daulat (BHGE, consultant)
• 15:49   BUG #15740: Problem with the creation of prodecures, synonyms and packages PG Bug reporting form
• 16:32   BUG #15741: ERROR: failed to build any 3-way joins PG Bug reporting form
• 16:41   Re: BUG #15740: Problem with the creation of prodecures, synonyms and packages Pavel Stehule
• 16:56   Re: BUG #15740: Problem with the creation of prodecures, synonyms andpackages André Free
• 16:57   Re: BUG #15740: Problem with the creation of prodecures, synonyms and packages Pavel Stehule
• 17:13   Re: BUG #15741: ERROR: failed to build any 3-way joins Tom Lane
• 17:20   Re: PostgreSQL 9.5 service stopped intermittently on windows 10 Proversion 1703. Julien Rouhaud
• 19:31   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Tom Lane
• 19:41   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Andres Freund
• 23:13   Re: BUG #15741: ERROR: failed to build any 3-way joins Tom Lane

9 April 2019

• 07:55   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Amit Langote
• 08:32   BUG #15742: Postgres Service is not starting after Windows abrupt Shutdown PG Bug reporting form
• 09:54   Re: BUG #15742: Postgres Service is not starting after Windowsabrupt Shutdown Michael Paquier
• 11:00   Re: BUG #15741: ERROR: failed to build any 3-way joins SKORSKI Anthony
• 12:26   RE: EXT: Re: PostgreSQL 9.5 service stopped intermittently on windows10 Pro version 1703. Kadam, Daulat (BHGE, consultant)
• 13:06   Re: EXT: Re: PostgreSQL 9.5 service stopped intermittently on windows10 Pro version 1703. Julien Rouhaud
• 16:59   BUG #15743: pg_tblspc Sharing violation with MSSQL, therefore PostgreSQL is running into Timeout at startup PG Bug reporting form
• 20:23   Re: BUG #15698: to_char doesn't return expected value with negativeINTERVAL Bruce Momjian
• 21:21   Re: BUG #15698: to_char doesn't return expected value with negative INTERVAL s.celles@gmail.com
• 23:09   BUG #15744: Replication slot peak query throwing error for wrong sequence entry for toast chunk PG Bug reporting form
• 23:29   BUG #15745: WAL References Invalid Pages...that eventually resolves PG Bug reporting form

10 April 2019

• 00:38   Unexpected behaviour, definitely looks like a bug. Leshchuk Aleksey
• 01:03   Re: Unexpected behaviour, definitely looks like a bug. Nikolay Samokhvalov
• 02:02   Re: Unexpected behaviour, definitely looks like a bug. David G. Johnston
• 04:17   Failure of initdb Bruce Rindahl
• 06:51   BUG #15746: cache lookup failed for function in plpgsql block PG Bug reporting form
• 09:04   Re: BUG #15734: Walsender process crashing when executing SHOW ALL; Michael Paquier
• 11:28   Re: BUG #15744: Replication slot peak query throwing error for wrongsequence entry for toast chunk Peter Eisentraut
• 18:01   Re: BUG #15734: Walsender process crashing when executing SHOW ALL; Alvaro Herrera
• 18:45   Re: BUG #15744: Replication slot peak query throwing error for wrongsequence entry for toast chunk Andres Freund
• 23:59   Re: BUG #15737: Unexpectedly Deleting full table when referring CTE(With Clause ) data,in a Subquery in another CTE Chandan Ahuja

11 April 2019

• 00:40   Suspicious strcmp() in src/backend/parser/parse_expr.c Rikard Falkeborn
• 01:33   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Andrew Gierth
• 01:43   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Tom Lane
• 05:19   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier
• 06:07   Re: BUG #15734: Walsender process crashing when executing SHOW ALL; Michael Paquier
• 06:26   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Thomas Munro
• 06:29   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
• 06:43   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c David Rowley
• 06:46   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier
• 06:47   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Michael Paquier
• 06:53   Re: BUG #15709: if drop exists syntax Jueve L
• 07:00   Re: BUG #15709: if drop exists syntax Pavel Stehule
• 07:17   Re: BUG #15709: if drop exists syntax Jueve L
• 07:17   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Жарков Роман
• 07:23   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Michael Paquier
• 07:32   Re: BUG #15709: if drop exists syntax Pavel Stehule
• 07:43   Re: BUG #15709: if drop exists syntax Jueve L
• 07:44   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Thomas Munro
• 07:47   Re: BUG #15709: if drop exists syntax Pavel Stehule
• 07:51   Re: BUG #15709: if drop exists syntax Jueve L
• 07:55   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Tom Lane
• 08:00   Re: BUG #15709: if drop exists syntax Pavel Stehule
• 08:35   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
• 09:50   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier
• 09:57   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Michael Paquier
• 09:57   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Michael Paquier
• 09:58   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 09:58   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 11:52   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Thomas Munro
• 11:53   BUG #15747: Help says 'application_name' property supports 64 characters in a standard built but it's only 63 PG Bug reporting form
• 11:55   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
• 11:58   Re: BUG #15747: Help says 'application_name' property supports 64 characters in a standard built but it's only 63 Sergei Kornilov
• 11:59   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Daniel Gustafsson
• 12:05   Re: BUG #15747: Help says 'application_name' property supports 64characters in a standard built but it's only 63 Tobias Gierke
• 13:51   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Thomas Munro
• 14:39   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Daniel Gustafsson
• 15:11   Re: BUG #15746: cache lookup failed for function in plpgsql block Kyotaro HORIGUCHI
• 15:50   BUG #15748: arrow keys doesn't work PG Bug reporting form
• 16:20   List of issues with 4.5 that need to be fixed Rossiter, Russell D.
• 16:58   Re: BUG #15748: arrow keys doesn't work Christoph Berg
• 17:06   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c David Rowley
• 17:12   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Tom Lane
• 18:01   Re: List of issues with 4.5 that need to be fixed Christopher Browne
• 18:04   Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Tom Lane
• 18:06   Re: List of issues with 4.5 that need to be fixed Alvaro Herrera

12 April 2019

• 03:58   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier
• 04:29   Re: Suspicious strcmp() in src/backend/parser/parse_expr.c Michael Paquier
• 05:44   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed r.zharkov@postgrespro.ru
• 06:22   Re: BUG #15746: cache lookup failed for function in plpgsql block r.zharkov@postgrespro.ru
• 06:32   Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker Michael Paquier
• 08:04   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Thomas Munro
• 08:19   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Michael Paquier
• 08:39   Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed Thomas Munro
• 16:38   BUG #15749: ERROR: dsa_area could not attach to segment | FATAL: cannot unpin a segment that is not pinned PG Bug reporting form
• 16:43   On replicas, checkpoints_req is incremented even if restartpoint hasnot happened Nikolay Samokhvalov
• 16:44   Re: BUG #15749: ERROR: dsa_area could not attach to segment | FATAL: cannot unpin a segment that is not pinned Sergei Kornilov
• 16:48   Re: BUG #15585: infinite DynamicSharedMemoryControlLock waiting in parallel query Sergei Kornilov
• 19:47   Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker Tom Lane
• 19:55   Re: BUG #15746: cache lookup failed for function in plpgsql block Tom Lane

13 April 2019

• 18:06   Re: Error occurred when i install in my pc. vinodh kumar gulumuru
• 18:27   Re: Error occurred when i install in my pc. vinodh kumar gulumuru
• 20:08   BUG #15750: don't have server PG Bug reporting form

14 April 2019

• 00:11   BUG #15751: Unexpected behaviour at plainto_tsquery funciton PG Bug reporting form
• 00:27   Re: BUG #15751: Unexpected behaviour at plainto_tsquery funciton Daniel Gustafsson
• 13:08   Re: Error occurred when i install in my pc. Sandeep Thakkar
• 14:51   BUG #15752: Declarative partitions trigger with function attributes - empty attributes list on each partition PG Bug reporting form
• 19:29   BUG #15753: FullText search cannot find bird, rat from birds, rats PG Bug reporting form
• 20:29   Re: BUG #15753: FullText search cannot find bird, rat from birds, rats Jeff Janes
• 22:36   BUG #15754: The CentOS RPM for PostgreSQL 11 disappeared and now throws a 404 error PG Bug reporting form

15 April 2019

• 06:39   Re: BUG #15734: Walsender process crashing when executing SHOW ALL; Michael Paquier
• 06:49   Re: Error occurred when i install in my pc. Sandeep Thakkar
• 07:30   Re: Error occurred when i install in my pc. vinodh kumar gulumuru
• 11:02   BUG #15755: After upgrading to 9.6.12 using pg_upgrade, select query does not return the expected results. PG Bug reporting form
• 13:01   BUG #15756: Seemingly inconsistent behavior of SUBSTRING(string FROM pattern FOR escape) function PG Bug reporting form
• 13:26   Re: BUG #15756: Seemingly inconsistent behavior of SUBSTRING(stringFROM pattern FOR escape) function Daniel Gustafsson
• 13:30   Re: BUG #15756: Seemingly inconsistent behavior of SUBSTRING(stringFROM pattern FOR escape) function Francisco Olarte
• 15:29   RE: [EXTERNAL] Re: List of issues with 4.5 that need to be fixed Rossiter, Russell D.
• 17:05   Re: BUG #15754: The CentOS RPM for PostgreSQL 11 disappeared and nowthrows a 404 error Tomas Vondra
• 19:15   Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, select query does not return the expected results. Tom Lane
• 21:30   BUG #15757: Problem with the sequences node PG Bug reporting form
• 21:37   Re: BUG #15757: Problem with the sequences node David G. Johnston

16 April 2019

• 05:11   Re: Error occurred when i install in my pc. vinodh kumar gulumuru
• 07:01   Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, selectquery does not return the expected results. Suresh Thelkar
• 09:31   Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, selectquery does not return the expected results. David G. Johnston
• 10:54   BUG #15758: regr_* return wrong answers for some valid data PG Bug reporting form
• 14:03   Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, selectquery does not return the expected results. Suresh Thelkar
• 14:04   BUG #15759: Lot of idle connection created by "SET extra_float_digits = 3" PG Bug reporting form
• 14:45   Re: BUG #15759: Lot of idle connection created by "SETextra_float_digits = 3" Tomas Vondra
• 15:01   Re: BUG #15759: Lot of idle connection created by "SET extra_float_digits = 3" anup singh
• 15:37   Re: BUG #15759: Lot of idle connection created by "SETextra_float_digits = 3" Tomas Vondra
• 16:00   BUG #15760: Error to start PGAdmin 4.5 PG Bug reporting form
• 16:35   Re: BUG #15759: Lot of idle connection created by "SETextra_float_digits = 3" anup singh
• 16:41   Re: BUG #15758: regr_* return wrong answers for some valid data Jeff Janes
• 17:10   BUG #15761: ODBC: SQLForeignKeys-ResultSet-Column 'deferrablity' PG Bug reporting form
• 17:40   Re: BUG #15759: Lot of idle connection created by "SETextra_float_digits = 3" Francisco Olarte
• 18:51   BUG #15762: Download URL not found PG Bug reporting form
• 19:54   Re: BUG #15758: regr_* return wrong answers for some valid data Dingyuan Wang
• 22:13   BUG #15763: JSON nulls not handled properly PG Bug reporting form
• 22:29   Re: BUG #15763: JSON nulls not handled properly Tom Lane
• 22:35   Re: BUG #15763: JSON nulls not handled properly David G. Johnston
• 22:57   Re: BUG #15763: JSON nulls not handled properly Jacob Crell
• 23:10   Re: BUG #15763: JSON nulls not handled properly Tom Lane

17 April 2019

• 05:24   BUG #15764: Yum repo/key name mismatch PG Bug reporting form
• 08:02   Re: Error occurred when i install in my pc. Sandeep Thakkar
• 08:12   Fw: PostgreSQL 11.2 , missing X509_get_signature_nid symbol causesthe standby to fail to start stream replication soumitra bhandary
• 10:02   Re: BUG #15764: Yum repo/key name mismatch Devrim Gündüz
• 10:55   BUG #15765: pgdg-redhat-repo-42.0-3 gpgkey entries don't exist in /etc/yum.repos.d/pgdg-redhat-all.repo PG Bug reporting form
• 10:55   Re: Fw: PostgreSQL 11.2 , missing X509_get_signature_nid symbol causes the standby to fail to start stream replication Devrim Gündüz
• 11:56   BUG #15766: discard plans bug. database CRASH PG Bug reporting form
• 12:16   BUG #15767: Export fails 'worker process died unexpectedly' but no error in pg_dump PG Bug reporting form
• 15:20   BUG #15768: Removed rpms and now require /etc/redhat-release PG Bug reporting form
• 15:32   Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, selectquery does not return the expected results. Suresh Thelkar
• 17:32   BUG #15769: The database cluster intialisation failed. PG Bug reporting form
• 18:44   Re: Error occurred when i install in my pc. vinodh kumar gulumuru
• 18:57   Re: BUG #15769: The database cluster intialisation failed. Tomas Vondra
• 19:07   Re: BUG #15768: Removed rpms and now require /etc/redhat-release Bruce Momjian
• 19:13   Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, selectquery does not return the expected results. Bruce Momjian
• 19:52   Re: BUG #15767: Export fails 'worker process died unexpectedly' but no error in pg_dump Tom Lane
• 20:00   Re: BUG #15766: discard plans bug. database CRASH Tom Lane
• 21:53   RE: Re: BUG #15769: The database cluster intialisation failed. Nick Anderson
• 22:15   Re: BUG #15703: Segfault in cancelled CALL-Statements Tom Lane
• 23:54   RE: Re: BUG #15769: The database cluster intialisation failed. Igor Neyman

18 April 2019

• 00:06   RE: Re: BUG #15769: The database cluster intialisation failed. Igor Neyman
• 04:37   回复：BUG #15766: discard plans bug. database CRASH 周正中(德歌)
• 06:11   pgAdmin bug? Fabrizio Mazzoni
• 09:38   BUG #15770: PostgreSQL rpm package got to be impossible to be installed in Amazon Linux 2 PG Bug reporting form
• 11:01   Re: BUG #15768: Removed rpms and now require /etc/redhat-release Devrim Gündüz
• 11:15   Re: Requiring temp tables to have replication identity defined Peter Eisentraut
• 12:27   BUG #15771: PgAdmin 4.5 don't listing sequences. PG Bug reporting form
• 14:18   Re: BUG #15768: Removed rpms and now require /etc/redhat-release Matt Harter
• 14:35   Installing latest psqlodbc rel 11.00.0000-x64 on windows server Maurizio Bellon
• 16:38   RE: Re: BUG #15769: The database cluster intialisation failed. Nick Anderson
• 16:53   BUG #15772: Some messages in log files are in ANSI encoding while server encoding is UTF8 PG Bug reporting form
• 17:31   Re: BUG #15772: Some messages in log files are in ANSI encodingwhile server encoding is UTF8 Bruce Momjian
• 17:40   Re: BUG #15772: Some messages in log files are in ANSI encoding while server encoding is UTF8 Eugene Podshivalov
• 18:29   Re: BUG #15772: Some messages in log files are in ANSI encodingwhile server encoding is UTF8 Bruce Momjian
• 19:01   Re: BUG #15772: Some messages in log files are in ANSI encodingwhile server encoding is UTF8 Alvaro Herrera
• 19:20   Re: BUG #15772: Some messages in log files are in ANSI encoding while server encoding is UTF8 Tom Lane
• 19:26   Re: BUG #15772: Some messages in log files are in ANSI encoding whileserver encoding is UTF8 Eugene Podshivalov
• 19:49   Re: BUG #15772: Some messages in log files are in ANSI encoding whileserver encoding is UTF8 Eugene Podshivalov

19 April 2019

• 15:45   Re: Re: BUG #15769: The database cluster intialisation failed. Sandeep Thakkar
• 16:29   BUG #15773: Cannot Open a sql file directly - have to go to pgadmin, query tool and then choose open PG Bug reporting form
• 17:21   Re: xpath insert unexpected newlines Tom Lane
• 19:48   RE: Re: Re: BUG #15769: The database cluster intialisation failed. Nick Anderson
• 21:55   BUG #15774: Postgresql installation error with BIGSql PG Bug reporting form

20 April 2019

• 04:15   amcheck assert failure Grigory Smolkin
• 04:30   Re: amcheck assert failure Peter Geoghegan
• 12:08   Re: amcheck assert failure Grigory Smolkin
• 22:26   Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
• 23:12   Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz

21 April 2019

• 00:00   Re: amcheck assert failure Peter Geoghegan
• 00:37   Re: amcheck assert failure Peter Geoghegan
• 02:06   Re: amcheck assert failure Peter Geoghegan
• 21:47   Segfault behaviour Азат Якупов
• 22:46   Re: Segfault behaviour Tom Lane

22 April 2019

• 04:50   Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
• 16:04   Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
• 16:42   Re: Possible to store invalid SCRAM-SHA-256 Passwords Tom Lane
• 16:52   Re: Possible to store invalid SCRAM-SHA-256 Passwords Stephen Frost
• 17:20   Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
• 19:03   Re: amcheck assert failure Grigory Smolkin
• 21:05   Re: amcheck assert failure Peter Geoghegan
• 22:48   Re: amcheck assert failure Grigory Smolkin
• 22:48   Re: xpath insert unexpected newlines Tom Lane
• 22:51   Re: amcheck assert failure Peter Geoghegan
• 22:51   Re: amcheck assert failure Tom Lane
• 23:31   Re: amcheck assert failure Peter Geoghegan
• 23:35   Re: amcheck assert failure Tom Lane
• 23:57   Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz

23 April 2019

• 00:49   Re: Possible to store invalid SCRAM-SHA-256 Passwords raf@raf.org
• 01:03   Re: amcheck assert failure Peter Geoghegan
• 01:32   Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
• 01:42   Re: Possible to store invalid SCRAM-SHA-256 Passwords Tom Lane
• 02:36   Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
• 02:55   Re: Possible to store invalid SCRAM-SHA-256 Passwords Tom Lane
• 03:06   Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
• 04:01   Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
• 04:10   Re: Possible to store invalid SCRAM-SHA-256 Passwords Tom Lane
• 04:16   Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
• 04:26   Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
• 04:28   Re: Possible to store invalid SCRAM-SHA-256 Passwords Tom Lane
• 05:10   Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
• 06:19   BUG #15775: pg_get_indexdef: could not open relation with OID 16385 PG Bug reporting form
• 09:57   Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
• 17:19   Re: Possible to store invalid SCRAM-SHA-256 Passwords Jonathan S. Katz
• 17:42   Re: Possible to store invalid SCRAM-SHA-256 Passwords Stephen Frost
• 17:43   Re: Possible to store invalid SCRAM-SHA-256 Passwords Stephen Frost
• 17:55   Re: Possible to store invalid SCRAM-SHA-256 Passwords Tom Lane
• 18:50   RE: Re: Re: BUG #15769: The database cluster intialisation failed. GOLLET Nicolas
• 19:42   BUG #15776: Pgpool PG Bug reporting form
• 21:30   Re: BUG #15776: Pgpool Jonathan S. Katz

24 April 2019

• 01:03   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Tom Lane
• 01:03   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Tom Lane
• 01:39   Re: BUG #15776: Pgpool Tatsuo Ishii
• 02:12   Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
• 03:07   Re: Possible to store invalid SCRAM-SHA-256 Passwords Michael Paquier
• 04:30   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 04:30   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 11:50   Re: amcheck assert failure Grigory Smolkin
• 14:35   bug: evil autoConcat when each string is on new line Jan Skydánek
• 14:56   Re: bug: evil autoConcat when each string is on new line Vik Fearing
• 15:44   Re: bug: evil autoConcat when each string is on new line Alvaro Herrera
• 16:13   BUG #15777: Unexpected error in select from view with set-returning function and union PG Bug reporting form
• 16:46   Re: BUG #15777: Unexpected error in select from view with set-returning function and union Sergei Kornilov
• 17:26   Re: bug: evil autoConcat when each string is on new line Tom Lane
• 20:07   CREATE SUBSCRIPTION fails with long passwords Mike Lissner
• 21:59   Re: amcheck assert failure Peter Geoghegan
• 22:42   BUG #15778: Replication slot peak query cause memory spike at the server when big transaction are running PG Bug reporting form
• 23:15   Re: amcheck assert failure Peter Geoghegan

25 April 2019

• 00:17   Re: CREATE SUBSCRIPTION fails with long passwords Tomas Vondra
• 02:13   Re: bug: evil autoConcat when each string is on new line raf@raf.org
• 02:27   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Tom Lane
• 02:27   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Tom Lane
• 03:59   Re: BUG #15631: Generated as identity field in a temporary tablewith on commit drop corrupts system catalogs Michael Paquier
• 05:21   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 05:21   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 09:27   Re: CREATE SUBSCRIPTION fails with long passwords Paul Mansueto Namuag
• 11:18   Re: bug: evil autoConcat when each string is on new line Francisco Olarte
• 12:43   Re: bug: evil autoConcat when each string is on new line Pavel Stehule
• 13:02   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 13:02   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 14:33   BUG #15779: Partition elimination doesn't work as expected when using PARTITION BY RANGE PG Bug reporting form
• 15:50   BUG #15780: Win10 PGS11 installer includes psAdmin3 LTS which does not support PGS11 PG Bug reporting form
• 16:32   BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) PG Bug reporting form
• 16:46   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Alvaro Herrera
• 16:46   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Alvaro Herrera
• 16:59   Re: CREATE SUBSCRIPTION fails with long passwords Tom Lane
• 17:03   Re: bug: evil autoConcat when each string is on new line Francisco Olarte
• 17:20   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Sergei Kornilov
• 17:45   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 17:45   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 21:24   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Tom Lane
• 21:24   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Tom Lane
• 23:20   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Dmitry Dolgov
• 23:20   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Dmitry Dolgov
• 23:27   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Tom Lane
• 23:27   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Tom Lane
• 23:36   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Tom Lane
• 23:36   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Tom Lane

26 April 2019

• 04:25   BUG #15782: Error in pgAdmin4.5 PG Bug reporting form
• 06:52   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 06:52   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Amit Langote
• 09:59   Re: BUG #15779: Partition elimination doesn't work as expected whenusing PARTITION BY RANGE Amit Langote
• 11:09   Re: BUG #15779: Partition elimination doesn't work as expected whenusing PARTITION BY RANGE Damir Ciganović-Janković
• 12:22   Reg: Postgresql8.3 Using on Ubuntu neelaveni
• 12:46   Re: Reg: Postgresql8.3 Using on Ubuntu Flo Rance
• 14:17   Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
• 15:21   Re: Reg: Postgresql8.3 Using on Ubuntu Flo Rance
• 15:39   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash(segfault) Etsuro Fujita
• 15:39   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash(segfault) Etsuro Fujita
• 15:44   Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
• 16:07   Re: BUG #15631: Generated as identity field in a temporary table withon commit drop corrupts system catalogs Peter Eisentraut
• 16:43   Re: Reg: Postgresql8.3 Using on Ubuntu Flo Rance
• 18:09   Re: BUG #15631: Generated as identity field in a temporary table with on commit drop corrupts system catalogs Tom Lane
• 18:39   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Alvaro Herrera
• 18:39   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table Alvaro Herrera
• 20:10   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Tom Lane
• 20:10   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Tom Lane
• 21:57   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Tom Lane
• 21:57   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Tom Lane

27 April 2019

• 00:21   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Tom Lane
• 00:21   Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Tom Lane
• 03:10   Re: BUG #15631: Generated as identity field in a temporary tablewith on commit drop corrupts system catalogs Michael Paquier
• 13:00   Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
• 14:45   Re: Reg: Postgresql8.3 Using on Ubuntu Andrew Gierth
• 16:30   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Etsuro Fujita
• 16:30   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Etsuro Fujita
• 17:47   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Tom Lane
• 17:47   Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) Tom Lane

28 April 2019

• 06:28   Re: BUG #15745: WAL References Invalid Pages...that eventually resolves Peter Geoghegan
• 07:09   BUG #15783: Fail to select with a function in FROM clause plus another table PG Bug reporting form
• 07:55   Re: BUG #15783: Fail to select with a function in FROM clause plus another table Tom Lane
• 09:47   BUG #15784: logical replication replicate data of type array for operation insert but update/delete/truncate PG Bug reporting form
• 14:14   Re: BUG #15784: logical replication replicate data of type array foroperation insert but update/delete/truncate Jeff Janes
• 18:50   Re: BUG #15779: Partition elimination doesn't work as expected whenusing PARTITION BY RANGE Amit Langote
• 20:32   Re: BUG #15779: Partition elimination doesn't work as expected whenusing PARTITION BY RANGE Damir Ciganović-Janković

29 April 2019

• 06:56   Re: BUG #15708: RLS 'using' running as wrong user when called from a view Daurnimator
• 06:56   Re: BUG #15708: RLS 'using' running as wrong user when called from a view Daurnimator
• 09:51   Re: Reg: Postgresql8.3 Using on Ubuntu Flo Rance
• 09:56   Re: BUG #15631: Generated as identity field in a temporary table withon commit drop corrupts system catalogs Peter Eisentraut
• 10:25   Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
• 10:42   crash of postgresql 11.2-2PGDG.rhel7 in StartupXLOG () atxlog.c:6355 Jozef Mlich
• 10:49   Re: BUG #15708: RLS 'using' running as wrong user when called from a view Dean Rasheed
• 10:49   Re: BUG #15708: RLS 'using' running as wrong user when called from a view Dean Rasheed
• 10:59   Re: Reg: Postgresql8.3 Using on Ubuntu Flo Rance
• 11:43   Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
• 11:43   BUG #15785: create slave through archive log replication PG Bug reporting form
• 11:49   Re: crash of postgresql 11.2-2PGDG.rhel7 in StartupXLOG () atxlog.c:6355 Jozef Mlich
• 13:17   Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
• 14:30   Re: Reg: Postgresql8.3 Using on Ubuntu neelaveni
• 16:03   Re: crash of postgresql 11.2-2PGDG.rhel7 in StartupXLOG () atxlog.c:6355 Michael Paquier

30 April 2019

• 00:46   BUG #15786: Matching version issue between postgres.exe and initdb.exe PG Bug reporting form
• 13:27   BUG #15787: Statement logging may consume huge amounts of memory when BYTEA parameters are involved. PG Bug reporting form
• 17:32   Re: BUG #15785: create slave through archive log replication Euler Taveira
• 17:49   RE: RE: Re: Re: BUG #15769: The database cluster intialisation failed. Nick Anderson
• 20:39   Current HEAD creates dumps that can't be loaded hubert depesz lubaczewski
• 22:44   Prepared statement is not re-parsed after used type is re-created -ERROR: cache lookup failed for type NNN Rashid Abzalov