pgsql-bugs since 2019-06-29 00:00

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

Search the Archives

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

Browse Archives

Prev | Next

June 29, 2019

Thread Author Time
Re: BUG #15858: could not stat file - over 4GB Michael Paquier 02:30
Re: BUG #15677: Crash while deleting from partitioned table Amit Langote 05:09
Re: BUG #15873: Attaching a partition fails because it sees deleted columns Amit Langote 05:13
Re: BUG #15858: could not stat file - over 4GB Juan José Santamaría Flecha 06:19
VACUUM FULL results in deadlock 📎 Manuel Rigger 15:51
Re: BUG #15121: Multiple UBSAN errors 📎 Noah Misch 21:03

June 30, 2019

Thread Author Time
Re: ERROR: virtual tuple table slot does not have system attributes Jeff Janes 00:47
Re: ERROR: virtual tuple table slot does not have system attributes Andres Freund 00:50
Re: BUG #15121: Multiple UBSAN errors Tom Lane 18:52

July 1, 2019

Thread Author Time
Re: BUG #15383: Join Filter cost estimation problem in 10.5 David Rowley 02:14

July 2, 2019

Thread Author Time
BUG #15882: Select .... UNION ALL PG Bug reporting form 08:28
Re: BUG #15882: Select .... UNION ALL David G. Johnston 09:22
ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation Manuel Rigger 10:06
GROUP BY and inheritance issue Manuel Rigger 12:47
Re: BUG #15882: Select .... UNION ALL David Rowley 12:55
[libpq] Segmentation fault when call PQfinish inside singletone pattern Ilya Galdin 12:56
Re: GROUP BY and inheritance issue David Rowley 13:13
BUG #15883: Event Trigger Firing Matrix Table is incomplete PG Bug reporting form 14:57
BUG #15884: json_object_agg errors on null in field name PG Bug reporting form 15:04
BUG #15885: EnterpriseDB Installer upgrade process fails with icacls error PG Bug reporting form 19:43
BUG #15886: I cannot install postgres PG Bug reporting form 21:03
Re: GROUP BY and inheritance issue Manuel Rigger 21:51
SELECT results in "ERROR: index key does not match expected index column" Manuel Rigger 22:00
Re: SELECT results in "ERROR: index key does not match expected index column" Tom Lane 22:50
Re: SELECT results in "ERROR: index key does not match expected index column" Gavin Flower 23:11
Re: SELECT results in "ERROR: index key does not match expected index column" Thomas Munro 23:44
Re: SELECT results in "ERROR: index key does not match expected index column" Tom Lane 23:45

July 3, 2019

Thread Author Time
Re: SELECT results in "ERROR: index key does not match expected index column" Peter Geoghegan 00:06
Re: SELECT results in "ERROR: index key does not match expected index column" Andrew Gierth 02:44
BUG #15887: An extra "break" instruction causes a bug PG Bug reporting form 03:04
BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot PG Bug reporting form 08:03
BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows PG Bug reporting form 09:10
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 09:41
Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows Juan José Santamaría Flecha 10:10
Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows Michael Paquier 11:35
Re: BUG #15890: Planner can't use index "(col) where col is not null" for query "where col in ($1, $2, ... $100+)" David Rowley 13:01
Cannot alter columns and add constraints in one alter statement since 11.4 update Maarten Jacobs 13:44
Re: BUG #15890: Planner can't use index "(col) where col is not null" for query "where col in ($1, $2, ... $100+)" Alexey Ermakov 13:49
BUG #15891: Cannot alter columns and add constraints in one alter statement since 11.4 update PG Bug reporting form 14:04
Re: BUG #15891: Cannot alter columns and add constraints in one alter statement since 11.4 update Tom Lane 14:49
Re: GROUP BY and inheritance issue David Rowley 22:11
BUG #15892: URGENT: Using an ICU collation in a primary key column breaks ILIKE query PG Bug reporting form 22:50
Re: GROUP BY and inheritance issue Manuel Rigger 23:06

July 4, 2019

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

July 5, 2019

Thread Author Time
Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" David G. Johnston 00:14
BUG #15895: pg_dump execution with OpenSSL encryption from Windows Service application PG Bug reporting form 07:01
BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« PG Bug reporting form 09:59
BUG #15897: make failed postgres 11.4 at 32 bit build PG Bug reporting form 11:10
Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Bernd Helmle 12:51
Re: BUG #15895: pg_dump execution with OpenSSL encryption from Windows Service application Robert Haas 13:08
Re: BUG #15897: make failed postgres 11.4 at 32 bit build Robert Haas 13:12
Re: BUG #15885: EnterpriseDB Installer upgrade process fails with icacls error Robert Haas 13:13
Re: VACUUM FULL results in deadlock Robert Haas 13:17
Re: BUG #15894: postgresql 9.5 will not install Robert Haas 13:25
Re: VACUUM FULL results in deadlock Manuel Rigger 13:26
Re: VACUUM FULL results in deadlock Robert Haas 13:31
Re: BUG #15886: I cannot install postgres Robert Haas 13:33
Re: [libpq] Segmentation fault when call PQfinish inside singletone pattern Robert Haas 13:54
Re: BUG #15897: make failed postgres 11.4 at 32 bit build Tom Lane 14:12
Re: BUG #15886: I cannot install postgres Euler Taveira 15:45
Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Alvaro Herrera 15:49
Re: VACUUM FULL results in deadlock Alvaro Herrera 16:14
Re: VACUUM FULL results in deadlock Tom Lane 17:08
BUG #15898: pg_dump error not able to restore complete dump PG Bug reporting form 19:11
Re: VACUUM FULL results in deadlock Tom Lane 20:57
Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan 22:14
Re: DISCARD TEMP results in "ERROR: cache lookup failed for type 0" Tom Lane 22:22
Re: VACUUM FULL results in deadlock Manuel Rigger 22:25
Re: VACUUM FULL results in deadlock Manuel Rigger 22:27
Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Peter Geoghegan 22:32
Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation Tom Lane 22:52
Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation Manuel Rigger 23:36

July 6, 2019

Thread Author Time
Re: BUG #15898: pg_dump error not able to restore complete dump David G. Johnston 07:41
Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« Christoph Berg 13:11
Re: ODBC: SQLGetDescField returns incorrect length for SQL_DESC_COUNT field of APD Bruce Momjian 20:31

July 7, 2019

Thread Author Time
VACUUM FULL results in ERROR: integer out of range 📎 Manuel Rigger 16:30
Re: VACUUM FULL results in ERROR: integer out of range Tom Lane 17:18
Re: VACUUM FULL results in ERROR: integer out of range Tom Lane 18:24
BUG #15899: Valgrind detects errors on create gist index PG Bug reporting form 19:10
Re: BUG #15899: Valgrind detects errors on create gist index 📎 Alexander Lakhin 19:21
Issue with CHAR column and "column LIKE column" condition Manuel Rigger 22:42

July 8, 2019

Thread Author Time
Re: Issue with CHAR column and "column LIKE column" condition Tom Lane 01:10
Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation Michael Paquier 06:01
PostgreSQL 11 can not restart after an unexpected shutdown Ádám Maracska 07:45
perl issue Prakash Ramakrishnan 07:57
PG11 - Multiple Key Range Partition Rares Salcudean 09:05
Re: PostgreSQL 11 can not restart after an unexpected shutdown Ádám Maracska 17:56
Re: PG11 - Multiple Key Range Partition David Rowley 21:48
BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks PG Bug reporting form 22:22
Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks Александр Акципетров 23:32
Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks 📎 Alex Aktsipetrov 23:39
Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks Thomas Munro 23:49

July 9, 2019

Thread Author Time
FDW does not push down LIMIT & ORDER BY with sharding (partitions) Gert van Dijk 00:12
Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks 📎 Thomas Munro 01:13
Re: BUG #15899: Valgrind detects errors on create gist index Michael Paquier 04:43
Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) Amit Langote 04:56
Re: PG11 - Multiple Key Range Partition Rares Salcudean 06:53
BUG #15901: Tablespace showing as null in psql and pgadmin PG Bug reporting form 09:14
BUG #15902: pgAdmin generates faulty SQL PG Bug reporting form 11:43
Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks Thomas Munro 11:47
Re: BUG #15901: Tablespace showing as null in psql and pgadmin Tom Lane 14:39
Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks Tom Lane 15:38
Re: BUG #15720: `executor could not find named tuplestore ABC` in AFTER DELETE trigger referencing OLD TABLE as ABC Tom Lane 15:45
Re: BUG #15720: `executor could not find named tuplestore ABC` in AFTER DELETE trigger referencing OLD TABLE as ABC Jason Madden 15:55
Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" Tom Lane 17:07
Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot Andres Freund 20:15
Re: BUG #15899: Valgrind detects errors on create gist index Andres Freund 20:59
Re: BUG #15752: Declarative partitions trigger with function attributes - empty attributes list on each partition Alvaro Herrera 21:26
Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot Alvaro Herrera 21:46
Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks Thomas Munro 22:43
Re: BUG #15720: `executor could not find named tuplestore ABC` in AFTER DELETE trigger referencing OLD TABLE as ABC Thomas Munro 22:46
Re: perl issue Alvaro Herrera 23:04
Re: PG11 - Multiple Key Range Partition David Rowley 23:32
ERROR: found unexpected null value in index 📎 Manuel Rigger 23:51

July 10, 2019

Thread Author Time
Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) David Rowley 00:38
Re: ERROR: found unexpected null value in index Peter Geoghegan 00:38
Re: perl issue Prakash Ramakrishnan 00:50
Re: ERROR: found unexpected null value in index Tom Lane 01:08
Re: ERROR: found unexpected null value in index Peter Geoghegan 01:30
Re: ERROR: found unexpected null value in index Tom Lane 01:43
Re: ERROR: found unexpected null value in index Peter Geoghegan 02:36
Re: ERROR: found unexpected null value in index Tom Lane 02:47
Re: ERROR: found unexpected null value in index Peter Geoghegan 03:06
Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot Michael Paquier 04:51
Re: BUG #15901: Tablespace showing as null in psql and pgadmin Ishan joshi 05:01
Re: BUG #15901: Tablespace showing as null in psql and pgadmin Thomas Kellerer 05:25
Re: BUG #15901: Tablespace showing as null in psql and pgadmin David G. Johnston 05:39
Re: BUG #15901: Tablespace showing as null in psql and pgadmin Ishan joshi 06:02
Re: PG11 - Multiple Key Range Partition Rares Salcudean 06:39
Re: BUG #15899: Valgrind detects errors on create gist index Michael Paquier 07:02
Re: BUG #15899: Valgrind detects errors on create gist index Michael Paquier 07:07
Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot Andres Freund 07:55
Re: PG11 - Multiple Key Range Partition David Rowley 08:37
Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) Amit Langote 08:47
Re: PG11 - Multiple Key Range Partition Amit Langote 09:01
Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows Haribabu Kommi 09:08
Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) Etsuro Fujita 09:34
Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) Gert van Dijk 09:39
Re: FDW does not push down LIMIT & ORDER BY with sharding (partitions) David Rowley 09:52
Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows Haribabu Kommi 09:53
Re: PG11 - Multiple Key Range Partition 📎 David Rowley 10:06
Re: PG11 - Multiple Key Range Partition Rares Salcudean 11:14
Re: perl issue vignesh C 11:30
BUG #15903: Getting error PG Bug reporting form 11:54
Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows Michael Paquier 12:51
Re: BUG #15903: Getting error David G. Johnston 13:52
Generated column and string concatenation issue Manuel Rigger 14:22
Re: Generated column and string concatenation issue Tom Lane 14:47
Re: Generated column and string concatenation issue Manuel Rigger 14:55
Re: Generated column and string concatenation issue Tom Lane 15:00
Re: Generated column and string concatenation issue Manuel Rigger 15:02
Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot Magnus Hagander 15:24
ERROR: negative bitmapset member not allowed in SELECT Manuel Rigger 15:39
Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows Juan José Santamaría Flecha 15:43
Re: ERROR: found unexpected null value in index 📎 Tom Lane 20:02
Re: ERROR: negative bitmapset member not allowed in SELECT Alvaro Herrera 20:09
Re: ERROR: found unexpected null value in index Andres Freund 20:15
Re: ERROR: negative bitmapset member not allowed in SELECT Tom Lane 20:17
Re: ERROR: found unexpected null value in index Tom Lane 20:25
Re: ERROR: found unexpected null value in index Andres Freund 20:36
Re: ERROR: found unexpected null value in index Tom Lane 20:48
Re: ERROR: found unexpected null value in index Peter Geoghegan 22:14
Re: ERROR: found unexpected null value in index Tom Lane 22:26
Re: ERROR: found unexpected null value in index Peter Geoghegan 23:08
Re: ERROR: found unexpected null value in index Tom Lane 23:29
Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot Michael Paquier 23:58

July 11, 2019

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

Browse Archives

Prev | Next