pgsql-bugs - January 2021

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

Search the Archives

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

Browse Archives

Prev | Next

Jan. 1, 2021

Thread Author Time
Re: BUG #16797: EXTRACT(EPOCH FROM timestamp) is not using local timezone Tom Lane 17:18
Re: BUG #16797: EXTRACT(EPOCH FROM timestamp) is not using local timezone Dana Burd 19:14
Re: BUG #16797: EXTRACT(EPOCH FROM timestamp) is not using local timezone Tom Lane 20:54

Jan. 2, 2021

Thread Author Time
BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs PG Bug reporting form 15:00

Jan. 3, 2021

Thread Author Time
Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs Michael Paquier 05:15
Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs Alexander Lakhin 06:00
Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs Michael Paquier 06:21

Jan. 4, 2021

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

Jan. 5, 2021

Thread Author Time
BUG #16805: "ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... PRIMARY KEY" fails if column exists and is the primary PG Bug reporting form 01:23
compiling error on OpenWrt baych igor 14:06
compiling error on OpenWrt baych igor 14:13
BUG #16806: postgresql10 rpm is installed in the wrong directory PG Bug reporting form 14:47
Re: BUG #16805: "ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... PRIMARY KEY" fails if column exists and is the primary Hamid Akhtar 15:05
Re: BUG #16805: "ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... PRIMARY KEY" fails if column exists and is the primary Tom Lane 15:45
Re: compiling error on OpenWrt Tom Lane 15:49
BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table PG Bug reporting form 18:00

Jan. 6, 2021

Thread Author Time
Re: compiling error on OpenWrt Michael Paquier 02:02
invalid resource manager ID 25 at 0/73C186B0 and db server can not join in cluster 📎 Li EF Zhang 02:07
Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table. Kasahara Tatsuhito 02:13
Re: BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table Etsuro Fujita 03:15
BUG #16808: Postgres Windows installer fails with unknown error and terminates PG Bug reporting form 03:25
BUG #16809: Package postgresql96-9.6.20-2PGDG.rhel7.x86_64 is not signed PG Bug reporting form 15:42
Re: BUG #16809: Package postgresql96-9.6.20-2PGDG.rhel7.x86_64 is not signed Devrim Gündüz 16:11
Re: BUG #16806: postgresql10 rpm is installed in the wrong directory Devrim Gündüz 17:53
BUG #16811: Severe reproducible server backend crash PG Bug reporting form 23:25

Jan. 7, 2021

Thread Author Time
Re: BUG #16811: Severe reproducible server backend crash 📎 James Inform 01:05
AW: BUG #16806: postgresql10 rpm is installed in the wrong directory 07:09
BUG #16812: Logical decoding error PG Bug reporting form 08:57
Re: BUG #16811: Severe reproducible server backend crash Thomas Munro 10:14
Re: BUG #16812: Logical decoding error mayur 11:15
AW: BUG #16806: postgresql10 rpm is installed in the wrong directory 13:00
BUG #16813: error to solve the problem "Windows could not stat file - over 4GB" PG Bug reporting form 14:02
Re: BUG #16811: Severe reproducible server backend crash Tom Lane 17:22
BUG #16814: Invalid memory access on regexp_match with .* and BRE PG Bug reporting form 19:00

Jan. 8, 2021

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

Jan. 9, 2021

Thread Author Time
Re: BUG #16808: Postgres Windows installer fails with unknown error and terminates Mihir Pandya 05:12

Jan. 11, 2021

Thread Author Time
Re: [ext] Re: BUG #16815: Unable to use the X448 an X25519 elliptic curves. Frank Büttner 11:39
Re: pg_upgrade test for binary compatibility of core data types Peter Eisentraut 14:28
BUG #16817: kill process cause postmaster hang PG Bug reporting form 15:10
Re: pg_upgrade test for binary compatibility of core data types Bruce Momjian 15:21
Re: BUG #16817: kill process cause postmaster hang Tom Lane 15:55
BUG #16818: progress reporting ALTER TABLE ADD UNIQUE PG Bug reporting form 19:31
Re: BUG #16818: progress reporting ALTER TABLE ADD UNIQUE 📎 Alvaro Herrera 21:13
Re: BUG #16818: progress reporting ALTER TABLE ADD UNIQUE Tom Lane 22:12
Re: BUG #16577: Segfault on altering a table located in a dropped tablespace 📎 Alvaro Herrera 23:42

Jan. 12, 2021

Thread Author Time
Re: pg_upgrade test for binary compatibility of core data types 📎 Justin Pryzby 04:13
Re: BUG #16812: Logical decoding error Amit Kapila 05:08
Re: BUG #16577: Segfault on altering a table located in a dropped tablespace Michael Paquier 06:34
BUG #16819: Bug Installation PG Bug reporting form 07:27
Re: SnapBuildSerialize function forgot pfree variable ondisk_c 📎 Amit Kapila 13:42
Re: BUG #16577: Segfault on altering a table located in a dropped tablespace Alvaro Herrera 15:08
Re: pg_upgrade test for binary compatibility of core data types Bruce Momjian 17:15
Re: pg_upgrade test for binary compatibility of core data types Justin Pryzby 17:27
Re: pg_upgrade test for binary compatibility of core data types Bruce Momjian 17:53
Re: pg_upgrade test for binary compatibility of core data types Andrew Dunstan 21:44

Jan. 13, 2021

Thread Author Time
Re: BUG #16808: Postgres Windows installer fails with unknown error and terminates michael wilder 03:57
Re: SnapBuildSerialize function forgot pfree variable ondisk_c Amit Kapila 05:40
Re: BUG #16577: Segfault on altering a table located in a dropped tablespace Michael Paquier 05:53
BUG #16820: PG will have a deadlock when multiple rows are updated concurrently PG Bug reporting form 07:43
Re: BUG #16812: Logical decoding error mayur 08:35
NO acceptable C compiler found in the $PATH Nikhil Saple 12:26
Re: BUG #16577: Segfault on altering a table located in a dropped tablespace Alvaro Herrera 12:57
BUG #16822: Unable to launch setup PG Bug reporting form 13:10
Re: NO acceptable C compiler found in the $PATH David G. Johnston 15:05
Re: NO acceptable C compiler found in the $PATH Tom Lane 15:13
BUG #16823: Unreachable code PG Bug reporting form 15:59
Re: BUG #16820: PG will have a deadlock when multiple rows are updated concurrently Tom Lane 16:26
Re: BUG #16823: Unreachable code Tom Lane 16:42
BUG #16824: Planner chooses poor path on query with Merge Join and pagination PG Bug reporting form 22:13

Jan. 14, 2021

Thread Author Time
Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination Tom Lane 00:16
Re: BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table 📎 Etsuro Fujita 02:56
Re: BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table Kyotaro Horiguchi 04:30
Re: BUG #16577: Segfault on altering a table located in a dropped tablespace Michael Paquier 04:49
questions about porting postgresql to older operating system Tim Kelly 16:39
Re: questions about porting postgresql to older operating system Tom Lane 18:18
Re: questions about porting postgresql to older operating system Heikki Linnakangas 18:34
Re: BUG #16577: Segfault on altering a table located in a dropped tablespace Alvaro Herrera 18:39
Re: questions about porting postgresql to older operating system Tom Lane 18:44

Jan. 15, 2021

Thread Author Time
Re: BUG #16812: Logical decoding error Amit Kapila 03:59
BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment PG Bug reporting form 07:48
Re: pg_upgrade test for binary compatibility of core data types Peter Eisentraut 08:00
BUG #16826: Regex in substring(... from ..) wrong PG Bug reporting form 08:23
BUG #16827: macOS interrupted syscall leads to a crash PG Bug reporting form 14:00
Re: BUG #16826: Regex in substring(... from ..) wrong David G. Johnston 14:20
syntactically correct query gives ERROR: failed to assign all NestLoopParams to plan nodes 📎 Stephan Springl 19:54
Re: BUG #16827: macOS interrupted syscall leads to a crash Andres Freund 21:05

Jan. 16, 2021

Thread Author Time
Re: BUG #16827: macOS interrupted syscall leads to a crash Ricardo Ungureanu 17:30
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 21:15
Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination Kisung Kim 22:34
Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination Tom Lane 23:28

Jan. 17, 2021

Thread Author Time
Re: syntactically correct query gives ERROR: failed to assign all NestLoopParams to plan nodes Tom Lane 02:18
Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data Noah Misch 07:24
RE: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment robionekenobi 08:31
BUG #16828: duplicate results when using ** recursive expression in JSON path PG Bug reporting form 10:34
RE: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment robionekenobi 18:22
Re: BUG #16828: duplicate results when using ** recursive expression in JSON path Tom Lane 19:42
Re: BUG #16828: duplicate results when using ** recursive expression in JSON path Alexander Korotkov 21:24
Re: BUG #16823: Unreachable code Rupert Gallagher 22:51

Jan. 18, 2021

Thread Author Time
Re: BUG #16822: Unable to launch setup Mihir Pandya 05:13
Re: BUG #16811: Severe reproducible server backend crash James Inform 08:30
BUG #16829: Postgresql-12 service is not starting with SSL enabled in centos 7 PG Bug reporting form 18:05
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 22:42
Re: BUG #16829: Postgresql-12 service is not starting with SSL enabled in centos 7 Juan José Santamaría Flecha 22:51

Jan. 19, 2021

Thread Author Time
Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier 05:23
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 08:31
Reproducible GIST index corruption under concurrent updates 📎 Duncan Sands 11:15
BUG #16830: Start of standby server never happens PG Bug reporting form 15:08
Re: Reproducible GIST index corruption under concurrent updates Andrey Borodin 17:12
Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas 21:53
Re: Reproducible GIST index corruption under concurrent updates 📎 Heikki Linnakangas 22:31

Jan. 20, 2021

Thread Author Time
Bug in error reporting for multi-line JSON 📎 Simon Riggs 06:58
Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier 07:24
Re: Reproducible GIST index corruption under concurrent updates Duncan Sands 08:23
Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas 10:04
Bug Report | Using ts_headline with the <-> operator christian 12:37
Re: Reproducible GIST index corruption under concurrent updates Tom Lane 15:25
Re: Bug Report | Using ts_headline with the <-> operator Tom Lane 15:38
BUG #16831: Idle postgres processes on Linux consumes huge amount of memory PG Bug reporting form 21:04
Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas 22:26
Re: BUG #16831: Idle postgres processes on Linux consumes huge amount of memory Tom Lane 23:19

Jan. 21, 2021

Thread Author Time
Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier 02:12
Problem with database Ijas MP 08:28
Проблемы с Postgresql 11 📎 Сибиряков Евгений Олегович 10:55
Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table. tomohiro hiramitsu 12:07
Re: Проблемы с Postgresql 11 Sergey Mirvoda 14:13
RE: BUG #16831: Idle postgres processes on Linux consumes huge amount of memory Li, Yaqing 15:40
Re: Problem with database Merlin Moncure 16:39
Re: Bug in error reporting for multi-line JSON Tom Lane 18:08
BUG #16832: Interrupted system call when working with large data tables PG Bug reporting form 22:16
segmentation fault in pg_restore with corrupt file Jon Snell 22:40

Jan. 22, 2021

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

Jan. 23, 2021

Thread Author Time
Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier 04:49
Re: BUG #16827: macOS interrupted syscall leads to a crash Ricardo Ungureanu 15:42
Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs Alvaro Herrera 21:44

Jan. 24, 2021

Thread Author Time
Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data 📎 Noah Misch 02:27
Re: BUG #16827: macOS interrupted syscall leads to a crash Kimon Krenz 23:03

Jan. 25, 2021

Thread Author Time
Re: BUG #16817: kill process cause postmaster hang bchen90 01:01
Re: BUG #16817: kill process cause postmaster hang Andy Fan 01:29
Re: BUG #16817: kill process cause postmaster hang Michael Paquier 01:35
[No subject] Dhanraj Acharya 05:46
BUG #16836: performance drop while query information_schema since switch from postgres 10 to 12 PG Bug reporting form 08:39
Re: Bug in error reporting for multi-line JSON Simon Riggs 13:08

Jan. 26, 2021

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

Jan. 27, 2021

Thread Author Time
Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs Alvaro Herrera 00:35
Re: BUG #16837: Invalid memory access on \h in psql Kyotaro Horiguchi 01:34
BUG #16838: notice is not displayed with in function PG Bug reporting form 10:15
BUG #16840: Rows not found in table partitioned by hash when not all partitions exists PG Bug reporting form 17:02
Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists Michał Albrycht 17:10
Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists Michał Albrycht 17:19
Inconsistent application of [, ...] in documentation Oliver Rice 17:27
Re: Inconsistent application of [, ...] in documentation David G. Johnston 17:59
Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists Tom Lane 18:08
Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs 📎 Alvaro Herrera 21:57
Re: Inconsistent application of [, ...] in documentation Oliver Rice 22:16
Re: Inconsistent application of [, ...] in documentation David G. Johnston 22:33
Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists 📎 Tom Lane 22:54

Browse Archives

Prev | Next