Mailing lists [pgsql-bugs]

1 January 2021

• 20:18   Re: BUG #16797: EXTRACT(EPOCH FROM timestamp) is not using local timezone Tom Lane
• 22:14   Re: BUG #16797: EXTRACT(EPOCH FROM timestamp) is not using local timezone Dana Burd
• 23:54   Re: BUG #16797: EXTRACT(EPOCH FROM timestamp) is not using local timezone Tom Lane

2 January 2021

• 18:00   BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs PG Bug reporting form

3 January 2021

• 08:15   Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs Michael Paquier
• 09:00   Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs Alexander Lakhin
• 09:21   Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs Michael Paquier

4 January 2021

• 07:46   how to prepare a create table statement Alexander Mills
• 13:51   Re: how to prepare a create table statement Pavel Stehule
• 13:55   Re: how to prepare a create table statement Michael Paquier
• 17:53   BUG #16803: create a table only one text/varchar column, storage options toast_tuple_target doesn't work PG Bug reporting form
• 20:48   BUG #16804: substring() function returns "negative substring length" error when using a large length argument PG Bug reporting form
• 21:00   Re: BUG #16774: PostgreSQL clean build MINGW64 gcc but initdb fails, cannot find startadress CreateProcessAsUserA Alexander Lakhin
• 21:15   Re: BUG #16803: create a table only one text/varchar column, storage options toast_tuple_target doesn't work Tom Lane
• 22:21   Re: BUG #16804: substring() function returns "negative substring length" error when using a large length argument Pavel Stehule
• 22:25   Re: BUG #16804: substring() function returns "negative substring length" error when using a large length argument Jerry Sievert
• 22:30   Re: BUG #16804: substring() function returns "negative substring length" error when using a large length argument Pavel Stehule

5 January 2021

• 00:28   Re: BUG #16804: substring() function returns "negative substring length" error when using a large length argument Tom Lane
• 00:52   Re: BUG #16804: substring() function returns "negative substring length" error when using a large length argument Rafi Shamim
• 01:28   Re: BUG #16804: substring() function returns "negative substring length" error when using a large length argument Tom Lane
• 04:23   BUG #16805: "ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... PRIMARY KEY" fails if column exists and is the primary PG Bug reporting form
• 17:06   compiling error on OpenWrt baych igor
• 17:13   compiling error on OpenWrt baych igor
• 17:47   BUG #16806: postgresql10 rpm is installed in the wrong directory PG Bug reporting form
• 18:05   Re: BUG #16805: "ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... PRIMARY KEY" fails if column exists and is the primary Hamid Akhtar
• 18:45   Re: BUG #16805: "ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... PRIMARY KEY" fails if column exists and is the primary Tom Lane
• 18:49   Re: compiling error on OpenWrt Tom Lane
• 21:00   BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table PG Bug reporting form

6 January 2021

• 05:02   Re: compiling error on OpenWrt Michael Paquier
• 05:13   Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table. Kasahara Tatsuhito
• 06:15   Re: BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table Etsuro Fujita
• 06:25   BUG #16808: Postgres Windows installer fails with iso-8859-1 error and terminates PG Bug reporting form
• 18:42   BUG #16809: Package postgresql96-9.6.20-2PGDG.rhel7.x86_64 is not signed PG Bug reporting form
• 19:11   Re: BUG #16809: Package postgresql96-9.6.20-2PGDG.rhel7.x86_64 is not signed Devrim Gündüz
• 20:53   Re: BUG #16806: postgresql10 rpm is installed in the wrong directory Devrim Gündüz

7 January 2021

• 02:25   BUG #16811: Severe reproducible server backend crash PG Bug reporting form
• 04:05   Re: BUG #16811: Severe reproducible server backend crash James Inform
• 10:09   AW: BUG #16806: postgresql10 rpm is installed in the wrong directory Kämpf, Heiko (OWL-IT)
• 11:57   BUG #16812: Logical decoding error PG Bug reporting form
• 13:14   Re: BUG #16811: Severe reproducible server backend crash Thomas Munro
• 14:15   Re: BUG #16812: Logical decoding error mayur
• 16:00   AW: BUG #16806: postgresql10 rpm is installed in the wrong directory Kämpf, Heiko (OWL-IT)
• 17:02   BUG #16813: error to solve the problem "Windows could not stat file - over 4GB" PG Bug reporting form
• 20:22   Re: BUG #16811: Severe reproducible server backend crash Tom Lane
• 22:00   BUG #16814: Invalid memory access on regexp_match with .* and BRE PG Bug reporting form

8 January 2021

• 04:59   Re: BUG #16813: error to solve the problem "Windows could not stat file - over 4GB" Michael Paquier
• 13:29   BUG #16815: Unable to use the X448 an X25519 elliptic curves. PG Bug reporting form
• 13:29   BUG #16816: Unexpected escaping of html output PG Bug reporting form
• 14:02   Re: BUG #16816: Unexpected escaping of html output Jeroen Baten
• 20:19   Re: BUG #16814: Invalid memory access on regexp_match with .* and BRE Tom Lane
• 23:46   Re: BUG #16815: Unable to use the X448 an X25519 elliptic curves. Tom Lane
• 23:57   Re: BUG #16815: Unable to use the X448 an X25519 elliptic curves. Tom Lane

9 January 2021

• 08:12   Re: BUG #16808: Postgres Windows installer fails with iso-8859-1 error and terminates Mihir Pandya

11 January 2021

• 14:39   Re: [ext] Re: BUG #16815: Unable to use the X448 an X25519 elliptic curves. Frank Büttner
• 18:10   BUG #16817: kill process cause postmaster hang PG Bug reporting form
• 18:55   Re: BUG #16817: kill process cause postmaster hang Tom Lane
• 22:31   BUG #16818: progress reporting ALTER TABLE ADD UNIQUE PG Bug reporting form

12 January 2021

• 00:13   Re: BUG #16818: progress reporting ALTER TABLE ADD UNIQUE Alvaro Herrera
• 01:12   Re: BUG #16818: progress reporting ALTER TABLE ADD UNIQUE Tom Lane
• 02:42   Re: BUG #16577: Segfault on altering a table located in a dropped tablespace Alvaro Herrera
• 08:08   Re: BUG #16812: Logical decoding error Amit Kapila
• 10:27   BUG #16819: Bug Installation PG Bug reporting form
• 16:42   Re: SnapBuildSerialize function forgot pfree variable ondisk_c Amit Kapila

13 January 2021

• 06:57   Re: BUG #16808: Postgres Windows installer fails with iso-8859-1 error and terminates michael wilder
• 08:40   Re: SnapBuildSerialize function forgot pfree variable ondisk_c Amit Kapila
• 10:43   BUG #16820: PG will have a deadlock when multiple rows are updated concurrently PG Bug reporting form
• 11:35   Re: BUG #16812: Logical decoding error mayur
• 15:26   NO acceptable C compiler found in the $PATH Nikhil Saple
• 16:10   BUG #16822: Unable to launch setup PG Bug reporting form
• 18:05   Re: NO acceptable C compiler found in the $PATH David G. Johnston
• 18:13   Re: NO acceptable C compiler found in the $PATH Tom Lane
• 18:59   BUG #16823: Unreachable code PG Bug reporting form
• 19:26   Re: BUG #16820: PG will have a deadlock when multiple rows are updated concurrently Tom Lane
• 19:42   Re: BUG #16823: Unreachable code Tom Lane

14 January 2021

• 01:13   BUG #16824: Planner chooses poor path on query with Merge Join and pagination PG Bug reporting form
• 03:16   Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination Tom Lane
• 05:56   Re: BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table Etsuro Fujita
• 07:30   Re: BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table Kyotaro Horiguchi
• 19:39   questions about porting postgresql to older operating system Tim Kelly
• 21:18   Re: questions about porting postgresql to older operating system Tom Lane
• 21:34   Re: questions about porting postgresql to older operating system Heikki Linnakangas
• 21:44   Re: questions about porting postgresql to older operating system Tom Lane

15 January 2021

• 06:59   Re: BUG #16812: Logical decoding error Amit Kapila
• 10:48   BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment PG Bug reporting form
• 11:23   BUG #16826: Regex in substring(... from ..) wrong PG Bug reporting form
• 17:00   BUG #16827: macOS interrupted syscall leads to a crash PG Bug reporting form
• 17:20   Re: BUG #16826: Regex in substring(... from ..) wrong David G. Johnston
• 22:54   syntactically correct query gives ERROR: failed to assign all NestLoopParams to plan nodes Stephan Springl

16 January 2021

• 00:05   Re: BUG #16827: macOS interrupted syscall leads to a crash Andres Freund
• 20:30   Re: BUG #16827: macOS interrupted syscall leads to a crash Ricardo Ungureanu

17 January 2021

• 00:15   Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Juan José Santamaría Flecha
• 01:34   Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination Kisung Kim
• 02:28   Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination Tom Lane
• 05:18   Re: syntactically correct query gives ERROR: failed to assign all NestLoopParams to plan nodes Tom Lane
• 11:31   RE: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment 
• 13:34   BUG #16828: duplicate results when using ** recursive expression in JSON path PG Bug reporting form
• 21:22   RE: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment 
• 22:42   Re: BUG #16828: duplicate results when using ** recursive expression in JSON path Tom Lane

18 January 2021

• 00:24   Re: BUG #16828: duplicate results when using ** recursive expression in JSON path Alexander Korotkov
• 01:51   Re: BUG #16823: Unreachable code Rupert Gallagher
• 08:13   Re: BUG #16822: Unable to launch setup Mihir Pandya
• 11:30   Re: BUG #16811: Severe reproducible server backend crash James Inform
• 21:05   BUG #16829: Postgresql-12 service is not starting with SSL enabled in centos 7 PG Bug reporting form

19 January 2021

• 01:42   Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Juan José Santamaría Flecha
• 01:51   Re: BUG #16829: Postgresql-12 service is not starting with SSL enabled in centos 7 Juan José Santamaría Flecha
• 08:23   Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier
• 11:31   Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Juan José Santamaría Flecha
• 14:15   Reproducible GIST index corruption under concurrent updates Duncan Sands
• 18:08   BUG #16830: Start of standby server never happens PG Bug reporting form
• 20:12   Re: Reproducible GIST index corruption under concurrent updates Andrey Borodin

20 January 2021

• 00:53   Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas
• 01:31   Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas
• 09:58   Bug in error reporting for multi-line JSON Simon Riggs
• 10:24   Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier
• 11:23   Re: Reproducible GIST index corruption under concurrent updates Duncan Sands
• 13:04   Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas
• 15:37   Bug Report | Using ts_headline with the <-> operator 
• 18:25   Re: Reproducible GIST index corruption under concurrent updates Tom Lane
• 18:38   Re: Bug Report | Using ts_headline with the <-> operator Tom Lane

21 January 2021

• 00:04   BUG #16831: Idle postgres processes on Linux consumes huge amount of memory PG Bug reporting form
• 01:26   Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas
• 02:19   Re: BUG #16831: Idle postgres processes on Linux consumes huge amount of memory Tom Lane
• 05:12   Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier
• 11:28   Problem with database Ijas MP
• 13:55   Проблемы с Postgresql 11 Сибиряков Евгений Олегович
• 15:07   Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table. tomohiro hiramitsu
• 17:13   Re: Проблемы с Postgresql 11 Sergey Mirvoda
• 18:40   RE: BUG #16831: Idle postgres processes on Linux consumes huge amount of memory Li, Yaqing
• 19:39   Re: Problem with database Merlin Moncure
• 21:08   Re: Bug in error reporting for multi-line JSON Tom Lane

22 January 2021

• 01:16   BUG #16832: Interrupted system call when working with large data tables PG Bug reporting form
• 01:40   segmentation fault in pg_restore with corrupt file Jon Snell
• 08:37   BUG #16833: postgresql 13.1 process crash every hour PG Bug reporting form
• 08:44   Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data Andrey Borodin
• 08:49   Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data Andrey Borodin
• 14:56   BUG #16834: where-in: if the nested query fails, the parent query returns all the records PG Bug reporting form
• 15:11   Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Jurko Gospodnetić
• 17:38   Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records Pantelis Theodosiou
• 17:48   Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records Pantelis Theodosiou
• 18:19   Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records Flavio Ricci
• 18:23   Re: BUG #16833: postgresql 13.1 process crash every hour Tom Lane
• 18:27   Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records David G. Johnston
• 18:56   BUG #16835: btree index does not work for where clause using 'foo%' PG Bug reporting form
• 19:44   Re: BUG #16835: btree index does not work for where clause using 'foo%' Tom Lane
• 20:21   Re: BUG #16833: postgresql 13.1 process crash every hour Alex F
• 20:24   Re: BUG #16832: Interrupted system call when working with large data tables Andres Freund
• 20:35   Re: BUG #16827: macOS interrupted syscall leads to a crash Andres Freund
• 20:47   Re: BUG #16827: macOS interrupted syscall leads to a crash Tom Lane
• 20:55   Re: BUG #16833: postgresql 13.1 process crash every hour Andres Freund
• 22:07   Re: [EXTERNAL] Re: BUG #16835: btree index does not work for where clause using 'foo%' Zhang, Hongyan
• 22:23   Re: [EXTERNAL] Re: BUG #16835: btree index does not work for where clause using 'foo%' luis.roberto@siscobra.com.br
• 22:45   Re: [EXTERNAL] Re: BUG #16835: btree index does not work for where clause using 'foo%' Zhang, Hongyan

23 January 2021

• 07:49   Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier

24 January 2021

• 00:44   Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs Alvaro Herrera

25 January 2021

• 02:03   Re: BUG #16827: macOS interrupted syscall leads to a crash Kimon Krenz
• 04:01   Re: BUG #16817: kill process cause postmaster hang bchen90
• 04:29   Re: BUG #16817: kill process cause postmaster hang Andy Fan
• 04:35   Re: BUG #16817: kill process cause postmaster hang Michael Paquier
• 08:46    Dhanraj Acharya
• 11:39   BUG #16836: performance drop while query information_schema since switch from postgres 10 to 12 PG Bug reporting form
• 16:08   Re: Bug in error reporting for multi-line JSON Simon Riggs

26 January 2021

• 10:00   BUG #16837: Invalid memory access on \h in psql PG Bug reporting form
• 11:26   Re: BUG #16827: macOS interrupted syscall leads to a crash Thomas Munro
• 12:07   Re: Bug in error reporting for multi-line JSON Hamid Akhtar
• 14:17   Re: BUG #16837: Invalid memory access on \h in psql Kyotaro Horiguchi
• 15:56   Assignment to composite type variable fails inside function but running query separately yields correct type & value ? Tobias Gierke
• 18:08   Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ? David G. Johnston
• 18:19   Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ? Tobias Gierke
• 19:11   Re: BUG #16837: Invalid memory access on \h in psql Tom Lane

27 January 2021

• 03:35   Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs Alvaro Herrera
• 04:34   Re: BUG #16837: Invalid memory access on \h in psql Kyotaro Horiguchi
• 13:15   BUG #16838: notice is not displayed with in function PG Bug reporting form
• 20:02   BUG #16840: Rows not found in table partitioned by hash when not all partitions exists PG Bug reporting form
• 20:27   Inconsistent application of [, ...] in documentation Oliver Rice
• 20:59   Re: Inconsistent application of [, ...] in documentation David G. Johnston
• 21:08   Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists Tom Lane

28 January 2021

• 00:57   Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs Alvaro Herrera
• 01:16   Re: Inconsistent application of [, ...] in documentation Oliver Rice
• 01:33   Re: Inconsistent application of [, ...] in documentation David G. Johnston
• 01:54   Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists Tom Lane
• 08:48   BUG #16841: psql -- \d tablename , displays "Error : column c.relhasoids does not exit" PG Bug reporting form
• 11:07   Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists Michał Albrycht
• 11:40   Re: BUG #16841: psql -- \d tablename , displays "Error : column c.relhasoids does not exit" Sergei Kornilov
• 11:54   Re: BUG #16841: psql -- \d tablename , displays "Error : column c.relhasoids does not exit" Ajay Chitale
• 12:00   Re: BUG #16838: notice is not displayed with in function Juan José Santamaría Flecha
• 12:06   Re: BUG #16841: psql -- \d tablename , displays "Error : column c.relhasoids does not exit" Magnus Hagander
• 12:36   Re: BUG #16841: psql -- \d tablename , displays "Error : column c.relhasoids does not exit" Ajay Chitale
• 15:19   BUG #16842: pg_dump uses seek calls on pipe files: suggesting adding a flag to disable seek calls PG Bug reporting form
• 15:53   BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed PG Bug reporting form
• 16:16   BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data PG Bug reporting form
• 18:32   Re: BUG #16842: pg_dump uses seek calls on pipe files: suggesting adding a flag to disable seek calls Tom Lane
• 18:34   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed Tom Lane
• 18:36   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed Bruce Momjian
• 18:43   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed Tom Lane
• 18:56   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed Bruce Momjian
• 22:59   Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs Alvaro Herrera
• 23:24   Re: BUG #16842: pg_dump uses seek calls on pipe files: suggesting adding a flag to disable seek calls Tomas Dalebjörk
• 23:57   Re: BUG #16842: pg_dump uses seek calls on pipe files: suggesting adding a flag to disable seek calls Tom Lane

29 January 2021

• 05:40   Re: BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data Kyotaro Horiguchi
• 05:53   Re: BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data Peter Geoghegan
• 10:14   Re: BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data Kyotaro Horiguchi
• 16:23   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed GMX Steffen
• 16:29   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed linreg@gmx.net
• 16:36   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed GMX LINREG
• 18:04   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed Tom Lane
• 19:40   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed GMX LINREG
• 20:29   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed Tom Lane
• 20:38   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed GMX LINREG
• 20:44   Re: BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data Lucas Valardao
• 20:55   Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed Tom Lane

30 January 2021

• 01:26   Re: Postgress 13.x: wrong result for delete with subquery Tom Lane
• 19:06   Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data Andrey Borodin

31 January 2021

• 01:41   Use of HAVING (Select/Group By) on a output-name of an aggregate function causes SYNTAX ERROR Carlos Sotto Maior \(UOL\)
• 01:46   Re: Use of HAVING (Select/Group By) on a output-name of an aggregate function causes SYNTAX ERROR Tom Lane
• 12:09   BUG #16846: "retrieved too many tuples in a bounded sort" PG Bug reporting form
• 14:33   Re: Use of HAVING (Select/Group By) on a output-name of an aggregate function causes SYNTAX ERROR Magnus Hagander
• 19:16   Re: BUG #16846: "retrieved too many tuples in a bounded sort" Tom Lane
• 19:35   Re: BUG #16846: "retrieved too many tuples in a bounded sort" Tom Lane