Home > mailing lists

Mailing lists [pgsql-bugs]

1 July 2019

05:14 Re: BUG #15383: Join Filter cost estimation problem in 10.5 David Rowley

2 July 2019

11:28 BUG #15882: Select .... UNION ALL PG Bug reporting form
12:22 Re: BUG #15882: Select .... UNION ALL David G. Johnston
13:06 ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation Manuel Rigger
15:47 GROUP BY and inheritance issue Manuel Rigger
15:55 Re: BUG #15882: Select .... UNION ALL David Rowley
15:56 [libpq] Segmentation fault when call PQfinish inside singletone pattern Ilya Galdin
16:13 Re: GROUP BY and inheritance issue David Rowley
17:57 BUG #15883: Event Trigger Firing Matrix Table is incomplete PG Bug reporting form
18:04 BUG #15884: json_object_agg errors on null in field name PG Bug reporting form
22:43 BUG #15885: EnterpriseDB Installer upgrade process fails with icacls error PG Bug reporting form

3 July 2019

00:03 BUG #15886: I cannot install postgres PG Bug reporting form
00:51 Re: GROUP BY and inheritance issue Manuel Rigger
01:00 SELECT results in "ERROR: index key does not match expected index column" Manuel Rigger
01:50 Re: SELECT results in "ERROR: index key does not match expected index column" Tom Lane
02:11 Re: SELECT results in "ERROR: index key does not match expected indexcolumn" Gavin Flower
02:44 Re: SELECT results in "ERROR: index key does not match expected index column" Thomas Munro
02:45 Re: SELECT results in "ERROR: index key does not match expected index column" Tom Lane
03:06 Re: SELECT results in "ERROR: index key does not match expected index column" Peter Geoghegan
05:44 Re: SELECT results in "ERROR: index key does not match expected index column" Andrew Gierth
06:04 BUG #15887: An extra "break" instruction causes a bug PG Bug reporting form
11:03 BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot PG Bug reporting form
12:10 BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows PG Bug reporting form
12:41 BUG #15890: Planner can't use index "(col) where col is not null" for query "where col in ($1, $2, ... $100+)" PG Bug reporting form
13:10 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 withMSVC on windows Juan José Santamaría Flecha
14:35 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 withMSVC on windows Michael Paquier
16:01 Re: BUG #15890: Planner can't use index "(col) where col is not null"for query "where col in ($1, $2, ... $100+)" David Rowley
16:44 Cannot alter columns and add constraints in one alter statement since11.4 update Maarten Jacobs
16:49 Re: BUG #15890: Planner can't use index "(col) where col is not null"for query "where col in ($1, $2, ... $100+)" Alexey Ermakov
17:04 BUG #15891: Cannot alter columns and add constraints in one alter statement since 11.4 update PG Bug reporting form
17:49 Re: BUG #15891: Cannot alter columns and add constraints in one alter statement since 11.4 update Tom Lane

4 July 2019

01:11 Re: GROUP BY and inheritance issue David Rowley
01:50 BUG #15892: URGENT: Using an ICU collation in a primary key column breaks ILIKE query PG Bug reporting form
02:06 Re: GROUP BY and inheritance issue Manuel Rigger
07:35 Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot Michael Paquier
10:35 BUG #15893: pg_dump is not working like as postgres version 10 PG Bug reporting form
10:46 Re: BUG #15893: pg_dump is not working like as postgres version 10 Michael Paquier
11:18 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 withMSVC on windows Juan José Santamaría Flecha
11:32 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 withMSVC on windows Michael Paquier
13:36 Re: BUG #15892: URGENT: Using an ICU collation in a primary keycolumn breaks ILIKE query Daniel Verite
15:59 DISCARD TEMP results in "ERROR: cache lookup failed for type 0" Manuel Rigger
16:06 Re: SELECT results in "ERROR: index key does not match expected index column" Manuel Rigger
16:11 Re: VACUUM FULL results in deadlock Manuel Rigger
17:00 BUG #15894: postgresql 9.5 will not install PG Bug reporting form
17:41 ALTER TABLE results in "ERROR: could not open relation with OID 43707388" Manuel Rigger
19:24 Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" David G. Johnston
19:40 Re: BUG #15892: URGENT: Using an ICU collation in a primary keycolumn breaks ILIKE query James Inform
19:40 Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" Manuel Rigger
19:50 Re: BUG #15892: URGENT: Using an ICU collation in a primary key column breaks ILIKE query Daniel Verite
20:06 Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" David G. Johnston
20:08 Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" Manuel Rigger
20:57 Re: BUG #15892: URGENT: Using an ICU collation in a primary keycolumn breaks ILIKE query Arthur Zakirov
21:12 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 withMSVC on windows Juan José Santamaría Flecha

5 July 2019

01:50 Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" Tom Lane
02:45 Re: ALTER TABLE results in "ERROR: could not open relation with OID43707388" Michael Paquier
02:48 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 withMSVC on windows Michael Paquier
03:14 Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" David G. Johnston
10:01 BUG #15895: pg_dump execution with OpenSSL encryption from Windows Service application PG Bug reporting form
12:59 BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« PG Bug reporting form
14:10 BUG #15897: make failed postgres 11.4 at 32 bit build PG Bug reporting form
15:51 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP:FailedAssertion(»!(metad->btm_version >= 3)« Bernd Helmle
16:08 Re: BUG #15895: pg_dump execution with OpenSSL encryption fromWindows Service application Robert Haas
16:12 Re: BUG #15897: make failed postgres 11.4 at 32 bit build Robert Haas
16:13 Re: BUG #15885: EnterpriseDB Installer upgrade process fails withicacls error Robert Haas
16:17 Re: VACUUM FULL results in deadlock Robert Haas
16:25 Re: BUG #15894: postgresql 9.5 will not install Robert Haas
16:26 Re: VACUUM FULL results in deadlock Manuel Rigger
16:31 Re: VACUUM FULL results in deadlock Robert Haas
16:33 Re: BUG #15886: I cannot install postgres Robert Haas
16:54 Re: [libpq] Segmentation fault when call PQfinish inside singletone pattern Robert Haas
17:12 Re: BUG #15897: make failed postgres 11.4 at 32 bit build Tom Lane
18:45 Re: BUG #15886: I cannot install postgres Euler Taveira
18:49 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Alvaro Herrera
19:14 Re: VACUUM FULL results in deadlock Alvaro Herrera
20:08 Re: VACUUM FULL results in deadlock Tom Lane
22:11 BUG #15898: pg_dump error not able to restore complete dump PG Bug reporting form
23:57 Re: VACUUM FULL results in deadlock Tom Lane

6 July 2019

01:14 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan
01:22 Re: DISCARD TEMP results in "ERROR: cache lookup failed for type 0" Tom Lane
01:25 Re: VACUUM FULL results in deadlock Manuel Rigger
01:27 Re: VACUUM FULL results in deadlock Manuel Rigger
01:32 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan
01:52 Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation Tom Lane
02:36 Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation Manuel Rigger
10:41 Re: BUG #15898: pg_dump error not able to restore complete dump David G. Johnston
16:11 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Christoph Berg
23:31 Re: ODBC: SQLGetDescField returns incorrect length forSQL_DESC_COUNT field of APD Bruce Momjian

7 July 2019

19:30 VACUUM FULL results in ERROR: integer out of range Manuel Rigger
20:18 Re: VACUUM FULL results in ERROR: integer out of range Tom Lane
21:24 Re: VACUUM FULL results in ERROR: integer out of range Tom Lane
22:10 BUG #15899: Valgrind detects errors on create gist index PG Bug reporting form
22:21 Re: BUG #15899: Valgrind detects errors on create gist index Alexander Lakhin

8 July 2019

01:42 Issue with CHAR column and "column LIKE column" condition Manuel Rigger
04:10 Re: Issue with CHAR column and "column LIKE column" condition Tom Lane
09:01 Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY indexcreation Michael Paquier
10:45 PostgreSQL 11 can not restart after an unexpected shutdown Ádám Maracska
10:57 perl issue Prakash Ramakrishnan
12:05 PG11 - Multiple Key Range Partition Rares Salcudean
20:56 Re: PostgreSQL 11 can not restart after an unexpected shutdown Ádám Maracska

9 July 2019

00:48 Re: PG11 - Multiple Key Range Partition David Rowley
01:22 BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks PG Bug reporting form
02:32 Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks Александр Акципетров
02:39 Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks Alex Aktsipetrov
02:49 Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks Thomas Munro
03:12 FDW does not push down LIMIT & ORDER BY with sharding (partitions) Gert van Dijk
04:13 Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks Thomas Munro
07:43 Re: BUG #15899: Valgrind detects errors on create gist index Michael Paquier
07:56 Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) Amit Langote
09:53 Re: PG11 - Multiple Key Range Partition Rares Salcudean
12:14 BUG #15901: Tablespace showing as null in psql and pgadmin PG Bug reporting form
14:43 BUG #15902: pgAdmin generates faulty SQL PG Bug reporting form
14:47 Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks Thomas Munro
17:39 Re: BUG #15901: Tablespace showing as null in psql and pgadmin Tom Lane
18:38 Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks Tom Lane
18:45 Re: BUG #15720: `executor could not find named tuplestore ABC` in AFTER DELETE trigger referencing OLD TABLE as ABC Tom Lane
18:55 Re: BUG #15720: `executor could not find named tuplestore ABC` inAFTER DELETE trigger referencing OLD TABLE as ABC Jason Madden
20:07 Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" Tom Lane
23:15 Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot Andres Freund
23:59 Re: BUG #15899: Valgrind detects errors on create gist index Andres Freund

10 July 2019

00:26 Re: BUG #15752: Declarative partitions trigger with functionattributes - empty attributes list on each partition Alvaro Herrera
00:46 Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot Alvaro Herrera
01:43 Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks Thomas Munro
01:46 Re: BUG #15720: `executor could not find named tuplestore ABC` inAFTER DELETE trigger referencing OLD TABLE as ABC Thomas Munro
02:04 Re: perl issue Alvaro Herrera
02:32 Re: PG11 - Multiple Key Range Partition David Rowley
02:51 ERROR: found unexpected null value in index Manuel Rigger
03:38 Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) David Rowley
03:38 Re: ERROR: found unexpected null value in index Peter Geoghegan
03:50 Re: perl issue Prakash Ramakrishnan
04:08 Re: ERROR: found unexpected null value in index Tom Lane
04:30 Re: ERROR: found unexpected null value in index Peter Geoghegan
04:43 Re: ERROR: found unexpected null value in index Tom Lane
05:36 Re: ERROR: found unexpected null value in index Peter Geoghegan
05:47 Re: ERROR: found unexpected null value in index Tom Lane
06:06 Re: ERROR: found unexpected null value in index Peter Geoghegan
07:51 Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot Michael Paquier
08:01 Re: BUG #15901: Tablespace showing as null in psql and pgadmin Ishan joshi
08:25 Re: BUG #15901: Tablespace showing as null in psql and pgadmin Thomas Kellerer
08:39 Re: BUG #15901: Tablespace showing as null in psql and pgadmin David G. Johnston
09:02 Re: BUG #15901: Tablespace showing as null in psql and pgadmin Ishan joshi
09:39 Re: PG11 - Multiple Key Range Partition Rares Salcudean
10:02 Re: BUG #15899: Valgrind detects errors on create gist index Michael Paquier
10:07 Re: BUG #15899: Valgrind detects errors on create gist index Michael Paquier
10:55 Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot Andres Freund
11:37 Re: PG11 - Multiple Key Range Partition David Rowley
11:47 Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) Amit Langote
12:01 Re: PG11 - Multiple Key Range Partition Amit Langote
12:08 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 withMSVC on windows Haribabu Kommi
12:34 Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) Etsuro Fujita
12:39 Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) Gert van Dijk
12:52 Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) David Rowley
12:53 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 withMSVC on windows Haribabu Kommi
13:06 Re: PG11 - Multiple Key Range Partition David Rowley
14:14 Re: PG11 - Multiple Key Range Partition Rares Salcudean
14:30 Re: perl issue vignesh C
14:54 BUG #15903: Getting error PG Bug reporting form
15:51 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 withMSVC on windows Michael Paquier
16:52 Re: BUG #15903: Getting error David G. Johnston
17:22 Generated column and string concatenation issue Manuel Rigger
17:47 Re: Generated column and string concatenation issue Tom Lane
17:55 Re: Generated column and string concatenation issue Manuel Rigger
18:00 Re: Generated column and string concatenation issue Tom Lane
18:02 Re: Generated column and string concatenation issue Manuel Rigger
18:24 Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot Magnus Hagander
18:39 ERROR: negative bitmapset member not allowed in SELECT Manuel Rigger
18:43 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 withMSVC on windows Juan José Santamaría Flecha
23:02 Re: ERROR: found unexpected null value in index Tom Lane
23:09 Re: ERROR: negative bitmapset member not allowed in SELECT Alvaro Herrera
23:15 Re: ERROR: found unexpected null value in index Andres Freund
23:17 Re: ERROR: negative bitmapset member not allowed in SELECT Tom Lane
23:25 Re: ERROR: found unexpected null value in index Tom Lane
23:36 Re: ERROR: found unexpected null value in index Andres Freund
23:48 Re: ERROR: found unexpected null value in index Tom Lane

11 July 2019

01:14 Re: ERROR: found unexpected null value in index Peter Geoghegan
01:26 Re: ERROR: found unexpected null value in index Tom Lane
02:08 Re: ERROR: found unexpected null value in index Peter Geoghegan
02:29 Re: ERROR: found unexpected null value in index Tom Lane
02:58 Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot Michael Paquier
03:52 Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks Andres Freund
10:18 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan
11:15 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Michael Paquier
13:48 The result of the pattern matching is incorrect when the patternstring is bpchar type 甄明洋
14:21 Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot Magnus Hagander
14:56 Re: ERROR: negative bitmapset member not allowed in SELECT Manuel Rigger
16:09 Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot Michael Paquier
16:44 Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot Tom Lane
17:36 Re: The result of the pattern matching is incorrect when the patternstring is bpchar type David G. Johnston
18:05 BUG #15904: ERROR: argument of LIMIT must not contain variables PG Bug reporting form
18:27 Re: BUG #15904: ERROR: argument of LIMIT must not contain variables David G. Johnston
19:26 Re: BUG #15904: ERROR: argument of LIMIT must not contain variables Lakradi Marwan
19:45 Re: BUG #15904: ERROR: argument of LIMIT must not contain variables David G. Johnston
20:26 Re: The result of the pattern matching is incorrect when the pattern string is bpchar type Andrew Gierth

12 July 2019

00:20 Re: ERROR: found unexpected null value in index Tom Lane
01:35 Re: ERROR: found unexpected null value in index Peter Geoghegan
02:01 Re: ERROR: found unexpected null value in index Tom Lane
04:25 Re: BUG #15888: Bogus "idle in transaction" state for logicaldecoding client after creating a slot Michael Paquier
06:31 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan
06:54 Re: PG11 - Multiple Key Range Partition David Rowley
07:23 Re: PG11 - Multiple Key Range Partition Michael Paquier
09:53 Re: PG11 - Multiple Key Range Partition Amit Langote
09:59 BUG #15905: FATAL: the database system is starting up PG Bug reporting form
10:14 Re: PG11 - Multiple Key Range Partition David Rowley
10:15 Re: BUG #15904: ERROR: argument of LIMIT must not contain variables Lakradi Marwan
10:57 Re: BUG #15905: FATAL: the database system is starting up Michael Paquier
11:27 Re: PG11 - Multiple Key Range Partition Amit Langote
21:45 Re: BUG #15905: FATAL: the database system is starting up Aayush Chaturvedi
22:18 The statement is re-executed (performed twice) on commit if it isdeclared as "cursor with hold" and the cursor is not closed yet Rashid Abzalov
23:19 Re: The statement is re-executed (performed twice) on commit if it isdeclared as "cursor with hold" and the cursor is not closed yet Rashid Abzalov
23:28 Re: ERROR: found unexpected null value in index Tom Lane
23:33 Re: The statement is re-executed (performed twice) on commit if it is declared as "cursor with hold" and the cursor is not closed yet Tom Lane

13 July 2019

02:18 Re: ERROR: found unexpected null value in index Manuel Rigger
08:49 Re: BUG #15905: FATAL: the database system is starting up Michael Paquier
11:37 BUG #15906: Insert ops within a branch of "RETURN QUERY WITH" are not seen by a subsequent SELECT PG Bug reporting form
14:07 Re: BUG #15906: Insert ops within a branch of "RETURN QUERY WITH" are not seen by a subsequent SELECT Andrew Gierth
16:12 Re: The statement is re-executed (performed twice) on commit if it isdeclared as "cursor with hold" and the cursor is not closed yet Rashid Abzalov

15 July 2019

00:30 SELECT with COLLATE results in segfault on trunk and 12 Beta 2 Manuel Rigger
01:22 Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2 Tom Lane
13:02 Three questions about Postgres Logical Replication Qinghui QH2 Guo
14:14 Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2 Manuel Rigger
19:03 Assertion fails with POSTGIS Ольга Ольга
20:50 Re: Assertion fails with POSTGIS Tom Lane
23:17 BUG #15907: JSON Select Issue PG Bug reporting form

16 July 2019

04:41 [BUG?] Missing OID column from pl/pgsql record Saul, Jean Paolo
04:47 Re: perl issue Prakash Ramakrishnan
05:01 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan
05:50 Re: [BUG?] Missing OID column from pl/pgsql record Tom Lane
06:44 Re: [BUG?] Missing OID column from pl/pgsql record Saul, Jean Paolo
07:49 Re: BUG #15907: JSON Select Issue Michael Paquier
09:01 Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2 Michael Paquier
11:13 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Christoph Berg
14:51 Re: perl issue vignesh C
14:55 BUG #15908: Xpath operations fail PG Bug reporting form
19:10 BUG #15909: Doc for `initdb` on `--data-checksums` says "cannot be changed later", but *can* be in Pg 12. PG Bug reporting form
19:19 BUG #15910: Valgrind-detected error in DecodeTimeOnly PG Bug reporting form
19:23 BUG #15911: Why no Bcrypt in pg_hba.conf? PG Bug reporting form
19:24 Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin
19:26 BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented PG Bug reporting form
19:33 Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2 Manuel Rigger
20:36 Re: BUG #15911: Why no Bcrypt in pg_hba.conf? Andrew Gierth
20:49 BUG #15913: Could not open relation with oid on PL/pgSQL method referencing temporary table that got recreated PG Bug reporting form
21:10 Re: BUG #15911: Why no Bcrypt in pg_hba.conf? Tom Lane
21:25 Re: ERROR: found unexpected null value in index Andres Freund
23:44 Re: BUG #15911: Why no Bcrypt in pg_hba.conf? Marco Sulla

17 July 2019

02:22 Re: BUG #15911: Why no Bcrypt in pg_hba.conf? raf
02:29 BETWEEN SYMMETRIC condition results in "row is too big: ..., maximumsize 8160" Manuel Rigger
02:52 Re: BETWEEN SYMMETRIC condition results in "row is too big: ..., maximum size 8160" Tom Lane
03:39 PLEASE HELP! Mary Kellen Park
03:47 BUG #15914: cannot get postgresql to work PG Bug reporting form
04:57 Re: BUG #15911: Why no Bcrypt in pg_hba.conf? Andrew Gierth
06:26 Re: BUG #15911: Why no Bcrypt in pg_hba.conf? Michael Paquier
06:30 Re: BUG #15909: Doc for `initdb` on `--data-checksums` says "cannotbe changed later", but *can* be in Pg 12. Michael Paquier
08:41 Re: PLEASE HELP! Fahar Abbas
10:57 Re: BUG #15909: Doc for `initdb` on `--data-checksums` says "cannotbe changed later", but *can* be in Pg 12. Daniel Gustafsson
15:53 REINDEX CONCURRENTLY causes ALTER TABLE to fail Manuel Rigger
17:54 Re: PLEASE HELP! Mary Kellen Park
18:40 Re: BUG #15908: Xpath operations fail Daniel Gustafsson
19:03 Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` settingshould be documented Daniel Gustafsson
21:11 transaction and insert jack chen
21:37 Re: transaction and insert David G. Johnston
21:43 Re: transaction and insert jack chen
21:50 Re: transaction and insert David G. Johnston
21:58 RE: transaction and insert Vianello, Daniel A
22:24 Re: transaction and insert David G. Johnston
22:31 Re: transaction and insert David G. Johnston

18 July 2019

00:24 User mapping: view over a foreign table Vladimir Ryabtsev
00:24 Re: User mapping: view over a foreign table Vladimir Ryabtsev
02:10 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan
02:51 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan
04:07 Re: BUG #15909: Doc for `initdb` on `--data-checksums` says "cannotbe changed later", but *can* be in Pg 12. Michael Paquier
06:02 Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail Michael Paquier
06:51 BUG #15915: ALTER COLUMN SET DATA TYPE fails with index already exists PG Bug reporting form
06:57 Re: BUG #15915: ALTER COLUMN SET DATA TYPE fails with index already exists Tom Lane
07:25 Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail Michael Paquier
11:32 BUG #15916: Confusing upgrade message PG Bug reporting form
12:19 Re: BUG #15893: pg_dump is not working like as postgres version 10 shaurya jain
12:30 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Christoph Berg
15:49 Re: BUG #15893: pg_dump is not working like as postgres version 10 Daniel Gustafsson
15:50 Re: ERROR: negative bitmapset member not allowed in SELECT Manuel Rigger
16:04 BUG #15917: Runtime Partition Pruning does not seem to work in PG 11 PG Bug reporting form
16:06 Re: BUG #15908: Xpath operations fail Daniel Gustafsson
16:46 RE: BUG #15908: Xpath operations fail Rick Vincent
17:15 Re: BUG #15908: Xpath operations fail Pavel Stehule
17:22 Re: BUG #15908: Xpath operations fail Tom Lane
17:27 Re: BUG #15908: Xpath operations fail Pavel Stehule
18:45 RE: BUG #15917: Runtime Partition Pruning does not seem to work in PG11 dbman@sqlexec.com
23:25 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan
23:57 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Alvaro Herrera

19 July 2019

00:27 Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan
04:40 BUG #15918: Startup of Postgresql PG Bug reporting form
05:50 Re: BUG #15893: pg_dump is not working like as postgres version 10 Michael Paquier
09:52 Re: BUG #15893: pg_dump is not working like as postgres version 10 shaurya jain
11:20 RE: BUG #15908: Xpath operations fail Rick Vincent
12:44 Re: BUG #15893: pg_dump is not working like as postgres version 10 Michael Paquier
13:06 Re: BUG #15893: pg_dump is not working like as postgres version 10 Thomas Kellerer
14:48 BUG #15919: When sorting, does the result show that S > s is correct? PG Bug reporting form
17:16 Re: BUG #15919: When sorting, does the result show that S > s is correct? Tom Lane

20 July 2019

19:54 Re: SELECT with COLLATE results in segfault on trunk and 12 Beta 2 Tom Lane

21 July 2019

02:56 BUG #15920: ERROR: deadlock detected PG Bug reporting form
06:19 Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail Tom Lane
06:27 Re: User mapping: view over a foreign table Tom Lane
21:53 Request for resolution || Support jay chauhan
23:48 Re: Request for resolution || Support David G. Johnston

22 July 2019

01:23 Re: Request for resolution || Support Thomas Munro
01:58 Re: Request for resolution || Support Jaime Casanova
14:12 BUG #15921: invalid regular expression while parsing hunspell affix PG Bug reporting form
14:16 Re: Logging corruption error codes Peter Eisentraut

23 July 2019

00:41 Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail Tom Lane
07:28 Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail Michael Paquier
11:07 A function privilege problem 高云龙
15:01 DROP STATISTICS results in "ERROR: tuple concurrently updated" Manuel Rigger
19:48 BUG #15922: Simple select with multiple exists filters returns duplicates from a primary key field PG Bug reporting form
19:50 Re: A function privilege problem Tom Lane
20:52 Re: BUG #15922: Simple select with multiple exists filters returns duplicates from a primary key field Tom Lane
21:14 Re: DROP STATISTICS results in "ERROR: tuple concurrently updated" Tom Lane
21:14 RE: BUG #15922: Simple select with multiple exists filters returnsduplicates from a primary key field David Raymond
23:00 Re: DROP STATISTICS results in "ERROR: tuple concurrently updated" Andres Freund

24 July 2019

00:42 RE: BUG #15922: Simple select with multiple exists filters returnsduplicates from a primary key field David Raymond
00:49 Re: BUG #15922: Simple select with multiple exists filters returns duplicates from a primary key field Tom Lane
01:46 partition table slow planning Jatinder Sandhu
04:19 ANALYZE on parent table results in an error "tuple already updated by self" Manuel Rigger
05:15 Re: ANALYZE on parent table results in an error "tuple alreadyupdated by self" Andres Freund
05:32 Re: ANALYZE on parent table results in an error "tuple alreadyupdated by self" Michael Paquier
08:35 Re: partition table slow planning Dilip Kumar
10:16 Attribute has wrong type in ALTER TABLE Manuel Rigger
10:17 Re: ANALYZE on parent table results in an error "tuple alreadyupdated by self" Manuel Rigger
13:00 ADD CHECK fails for parent table if column used in CHECK is fully-qualified Manuel Rigger
18:33 RE: BUG #15922: Simple select with multiple exists filters returnsduplicates from a primary key field David Raymond
19:08 Re: Request for resolution || Support Christopher Browne
20:06 Re: BUG #15922: Simple select with multiple exists filters returns duplicates from a primary key field Tom Lane
21:02 Re: Attribute has wrong type in ALTER TABLE Tom Lane
21:15 RE: BUG #15922: Simple select with multiple exists filters returnsduplicates from a primary key field David Raymond

25 July 2019

00:39 BUG #15923: Prepared statements take way too much memory. PG Bug reporting form
01:23 Re: BUG #15923: Prepared statements take way too much memory. Tom Lane
01:32 AW: BUG #15923: Prepared statements take way too much memory. Daniel Migowski
04:54 Re: ERROR: virtual tuple table slot does not have system attributes Andres Freund
05:05 Re: A function privilege problem 高云龙
05:09 Re: ADD CHECK fails for parent table if column used in CHECK is fully-qualified Tom Lane
06:08 Re: A function privilege problem David G. Johnston
08:56 AW: BUG #15923: Prepared statements take way too much memory. Daniel Migowski
13:31 Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail Michael Paquier
13:45 Re: Logging corruption error codes Andrey Borodin
18:59 BUG #15924: Query Execution and variable declaration PG Bug reporting form
19:13 Re: BUG #15827: Unable to connect on Windows using pg_services.conf using Python psycopg2 Tom Lane
19:43 Re: BUG #15924: Query Execution and variable declaration David G. Johnston
19:43 Re: BUG #15827: Unable to connect on Windows using pg_services.conf using Python psycopg2 Jorge Gustavo Rocha
21:27 Re: Logging corruption error codes Peter Geoghegan

26 July 2019

01:13 Re: AW: BUG #15923: Prepared statements take way too much memory. Tom Lane
01:55 Re: AW: BUG #15923: Prepared statements take way too much memory. Thomas Munro
03:34 Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail Michael Paquier
03:41 Re: BUG #15923: Prepared statements take way too much memory. Andres Freund
04:04 Re: BUG #15923: Prepared statements take way too much memory. Andres Freund
05:16 Re: BUG #15923: Prepared statements take way too much memory. Andres Freund
06:56 Re: A function privilege problem 高云龙
07:58 Re: BUG #15827: Unable to connect on Windows using pg_services.confusing Python psycopg2 Michael Paquier
10:39 BUG #15925: Loss of precision converting money to numeric PG Bug reporting form
16:16 BUG #15926: TPCH Q18 slow: explain plan with 2 step Hash Aggregate (partial and finalize) PG Bug reporting form
16:55 Error CREATE EXTENSION plpythonu milad moradi
17:16 Re: Error CREATE EXTENSION plpythonu Fahar Abbas
17:20 Re: Error CREATE EXTENSION plpythonu Fahar Abbas
18:17 Re: BUG #15925: Loss of precision converting money to numeric Tom Lane
19:15 Re: BUG #15925: Loss of precision converting money to numeric Slawomir Chodnicki
21:11 BUG #15927: PGresult *PQexecParams(..) not work on view PG Bug reporting form
21:21 Re: BUG #15927: PGresult *PQexecParams(..) not work on view Andres Freund
21:21 BUG #15928: Message no longer displaying rows affected with insert and update statements PG Bug reporting form

27 July 2019

00:43 Possible Problem with pgAdmin 4.11 Joseph Ruffino
01:02 Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` settingshould be documented Alvaro Herrera
01:19 Re: Attribute has wrong type in ALTER TABLE Manuel Rigger
01:20 Re: DISCARD TEMP results in "ERROR: cache lookup failed for type 0" Alvaro Herrera
12:21 Multiple inheritance and ALTER TABLE issue Manuel Rigger
12:39 BUG #15929: logical decoding can not write down the analyse result when the output file is touched. PG Bug reporting form
18:16 BUG #15930: Redact PGPASSWORD environment variable in psql PG Bug reporting form
18:23 Re: BUG #15930: Redact PGPASSWORD environment variable in psql Tom Lane
19:53 Re: Multiple inheritance and ALTER TABLE issue Tom Lane

28 July 2019

00:41 Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` settingshould be documented Bruce Momjian
03:47 Re: BUG #15916: Confusing upgrade message Bruce Momjian
13:45 Re: BUG #15883: Event Trigger Firing Matrix Table is incomplete Michael Paquier
14:14 RE: BUG #15923: Prepared statements take way too much memory. Daniel Migowski
16:04 Re: BUG #15883: Event Trigger Firing Matrix Table is incomplete Michael Paquier
21:56 PostgreSQL12 crash bug report yi huang
23:11 Re: PostgreSQL12 crash bug report Tom Lane

29 July 2019

04:10 Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail Michael Paquier
08:15 GoldenGate to PostgreSQL connectivity Murali Krishna
09:11 Re: BUG #15923: Prepared statements take way too much memory. Thomas Munro
10:22 Re: REINDEX CONCURRENTLY causes ALTER TABLE to fail Manuel Rigger
12:41 BUG #15931: PSQL in version 7.6 even though I installed PostgreSQL 10 PG Bug reporting form
12:55 AW: BUG #15923: Prepared statements take way too much memory. Daniel Migowski
14:19 RE: GoldenGate to PostgreSQL connectivity Greg Clough
18:56 BUG #15932: Module passwordcheck doesn't reference previous hooks PG Bug reporting form
21:37 Re: BUG #15930: Redact PGPASSWORD environment variable in psql Georg Sauthoff

30 July 2019

05:24 Re: BUG #15932: Module passwordcheck doesn't reference previous hooks Michael Paquier
05:29 Re: BUG #15930: Redact PGPASSWORD environment variable in psql Michael Paquier
06:59 Re: BUG #15923: Prepared statements take way too much memory. Kyotaro Horiguchi
10:53 BUG #15933: Partition by multiple columns bug PG Bug reporting form
17:34 Re: BUG #15933: Partition by multiple columns bug Tom Lane

31 July 2019

07:58 Re: BUG #15933: Partition by multiple columns bug Amit Langote
08:26 Re: BUG #15933: Partition by multiple columns bug Damir Ciganović-Janković
09:07 Re: Logging corruption error codes Andrey Borodin
10:15 Re: BUG #15932: Module passwordcheck doesn't reference previous hooks Michael Paquier
10:23 Re: BUG #15932: Module passwordcheck doesn't reference previous hooks Daniel Gustafsson
10:34 Re: BUG #15932: Module passwordcheck doesn't reference previous hooks Michael Paquier
10:54 Re: BUG #15932: Module passwordcheck doesn't reference previous hooks Daniel Gustafsson
11:55 UPDATE with json_populate_recordset empty array crashes server Marks Polakovs
12:54 Re: UPDATE with json_populate_recordset empty array crashes server Sergei Kornilov
13:12 BUG #15934: pg_dump output in wrong order if custom operator class is used as subtype_opclass in a range type PG Bug reporting form
14:30 BUG #15935: Auto increment column changes on error while inserting (violating unique constraint) PG Bug reporting form
16:36 RE: BUG #15935: Auto increment column changes on error whileinserting (violating unique constraint) David Raymond
19:07 Re: BUG #15934: pg_dump output in wrong order if custom operator class is used as subtype_opclass in a range type Tom Lane
21:26 Re: BUG #15934: pg_dump output in wrong order if custom operator class is used as subtype_opclass in a range type Tom Lane