Mailing lists [pgsql-bugs]

1 March

• 00:31   Re: Record returning function accept not matched columns declaration David G. Johnston
• 00:55   Re: Record returning function accept not matched columns declaration David G. Johnston
• 01:01   Re: Record returning function accept not matched columns declaration PetSerAl
• 01:17   Record returning function accept not matched columns declaration Wetmore, Matthew (CTR)
• 01:31   Re: Record returning function accept not matched columns declaration Tom Lane
• 04:53   Re: BUG #18362: unaccent rules and Old Greek text Thomas Munro
• 05:14   Re: `order by random()` makes select-list `random()` invocations deterministic Dian Fay
• 05:46   Re: `order by random()` makes select-list `random()` invocations deterministic Tom Lane
• 07:31   Re: Facing issue in installing pg_cron extension in Postgresql 15 Noah Misch
• 11:56   FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 12:12   Re: FSM Corruption (was: Could not read block at end of the relation) Michael Paquier
• 12:50   Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker Alexey Ermakov
• 15:48   Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker Andrei Lepikhov
• 18:54   Re: BUG #18362: unaccent rules and Old Greek text Cees van Zeeland
• 18:54   Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker Alexey Ermakov
• 20:55   Re: Record returning function accept not matched columns declaration Tom Lane

2 March

• 09:00   BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault PG Bug reporting form
• 19:11   Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault Tom Lane
• 20:00   Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault Alexander Lakhin
• 21:49   Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault Tom Lane
• 22:58   Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault Tom Lane

4 March

• 00:39   Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault Tom Lane
• 01:12   Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker Thomas Munro
• 02:47   Re: FSM Corruption (was: Could not read block at end of the relation) Noah Misch
• 02:49   Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker Tomas Vondra
• 03:00   Re: Record returning function accept not matched columns declaration jian he
• 03:07   relfrozenxid may disagree with row XIDs after 1ccc1e05ae Noah Misch
• 03:11   Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker Thomas Munro
• 03:20   Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker Thomas Munro
• 03:40   Re: Record returning function accept not matched columns declaration Tom Lane
• 10:19   BUG #18375: requested statistics kind "f" is not yet built for statistics object 16722 PG Bug reporting form
• 11:35   RE:Undetected deadlock between client backend and startup processes on a standby (Previously, Undetected deadlock between primary and standby processes)  
• 12:56   BUG #18376: pg_upgrade fails trying to restore privileges on retired function pg_start_backup and pg_stop_backup PG Bug reporting form
• 15:52   RE: BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)
• 16:10   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 18:00   Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault Alexander Lakhin
• 20:11   Re: BUG #18375: requested statistics kind "f" is not yet built for statistics object 16722 Tom Lane
• 22:03   Re: FSM Corruption (was: Could not read block at end of the relation) Noah Misch

5 March

• 01:21   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 01:45   Re: BUG #18376: pg_upgrade fails trying to restore privileges on retired function pg_start_backup and pg_stop_backup Michael Paquier
• 02:05   Re: FSM Corruption (was: Could not read block at end of the relation) Noah Misch
• 02:33   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 03:13   Re: FSM Corruption (was: Could not read block at end of the relation) Noah Misch
• 03:35   Re: BUG #18375: requested statistics kind "f" is not yet built for statistics object 16722 David Rowley
• 03:56   Re: FSM Corruption (was: Could not read block at end of the relation) Michael Paquier
• 04:09   Re: BUG #18375: requested statistics kind "f" is not yet built for statistics object 16722 Richard Guo
• 06:13   Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently Michael Paquier
• 06:20   Re: BUG #18375: requested statistics kind "f" is not yet built for statistics object 16722 David Rowley
• 06:37   BUG #18377: Assert false in "partdesc->nparts >= pinfo->nparts", fileName="execPartition.c", lineNumber=1943 PG Bug reporting form
• 06:44   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Michael Paquier
• 07:00   Re: BUG #18369: logical decoding core on AssertTXNLsnOrder() Alexander Lakhin
• 07:12   Query stuck with wait event IPC / ParallelFinish Jeff Davis
• 09:21   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Tender Wang
• 09:58   BUG #18378: postgis protobuf support inconsistent PG Bug reporting form
• 10:37   Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently alvherre
• 11:09   Re: BUG #18378: postgis protobuf support inconsistent Devrim Gündüz
• 11:24   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Tender Wang
• 11:57   Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently 费长红
• 12:24   RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)
• 14:49   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Tender Wang
• 15:15   bug in function strtoint, on Windows OS won't report ERANGE Miron Berlin
• 16:22   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build jian he
• 16:34   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 17:38   Issue with PostgreSQL 11 RPM Package Availability Said Krikess
• 18:42   Re: bug in function strtoint, on Windows OS won't report ERANGE Tom Lane
• 21:00   Re: BUG #18351: VACUUM FULL fails with error: missing chunk number 0 for toast value XXX Alexander Lakhin

6 March

• 01:45   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Michael Paquier
• 02:12   Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently Michael Paquier
• 05:09   Re: BUG #18377: Assert false in "partdesc->nparts >= pinfo->nparts", fileName="execPartition.c", lineNumber=1943 David Rowley
• 06:33   Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() ocean_li_996
• 06:35   Re: Issue with PostgreSQL 11 RPM Package Availability Bruce Momjian
• 07:30   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Tender Wang
• 11:51   A build failure since only include header "postgresql/server/port.h" Changqing Li
• 12:31   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 13:35   Re: Issue with PostgreSQL 11 RPM Package Availability Devrim Gündüz
• 13:59   Re: FSM Corruption (was: Could not read block at end of the relation) Patrick Stählin
• 14:08   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 15:07   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Tender Wang
• 16:51   BUG #18379: LDAP bind password exposed PG Bug reporting form
• 19:00   Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault Alexander Lakhin
• 20:28   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Tom Lane
• 21:40   Re: BUG #18379: LDAP bind password exposed Stephen Frost
• 21:42   Re: FSM Corruption (was: Could not read block at end of the relation) Noah Misch
• 22:52   Re: BUG #18379: LDAP bind password exposed Tom Lane
• 23:09   Re: Record returning function accept not matched columns declaration Tom Lane
• 23:24   Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault Alexander Korotkov

7 March

• 00:18   BUG #18380: BUG: notify stops working after LEFT JOIN if enable_mergejoin is ON PG Bug reporting form
• 00:21   Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault Tom Lane
• 01:40   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Michael Paquier
• 02:01   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Tom Lane
• 02:42   Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build Michael Paquier
• 07:45   RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)
• 09:34   Re: BUG #18379: LDAP bind password exposed Stephen Frost
• 13:22   BUG #18381: Invalid query generated by postgres_fdw with UNION ALL and ORDER BY PG Bug reporting form
• 14:21   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 14:32   Re: BUG #18381: Invalid query generated by postgres_fdw with UNION ALL and ORDER BY David Rowley
• 16:17   Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction Maxim Orlov
• 16:34   Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction Alexander Korotkov
• 20:58   BUG #18383: creation of public schema is not consistent PG Bug reporting form
• 22:47   Re: BUG #18383: creation of public schema is not consistent Sam Darwin
• 23:11   Re: BUG #18383: creation of public schema is not consistent Tom Lane

8 March

• 04:48   Re: BUG #18383: creation of public schema is not consistent Sam Darwin
• 09:00   BUG #18384: It's not bug just question about documentation PG Bug reporting form
• 10:31   Re: BUG #18383: creation of public schema is not consistent Laurenz Albe
• 10:35   RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)
• 12:55   facing an issue with the installation of pljava 1.6.6.  Shankarigari Ashok
• 15:59   Re: RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Amit Kapila
• 18:28   Re: BUG #18384: It's not bug just question about documentation Tom Lane

9 March

• 07:50   RE: RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)

10 March

• 22:00   BUG #18385: Assert("strategy_delta >= 0") in BgBufferSync() fails due to race condition PG Bug reporting form
• 23:43   Re: Undetected deadlock between client backend and startup processes on a standby (Previously, Undetected deadlock between primary and standby processes) Tomas Vondra

11 March

• 11:12   Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker Alexey Ermakov
• 15:48   BUG #18386: Slow connection access after 'vacuum full pg_attribute' PG Bug reporting form
• 19:43   Re:RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() ocean_li_996
• 23:10   BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view PG Bug reporting form

12 March

• 01:13   BUG #18388: Server freezes after AuthenticationSASLFinal message PG Bug reporting form
• 01:19   A server crash with a SQL procedure returning a user-defined type on 14.8 Yahor Yuzefovich
• 02:02   Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view Heikki Linnakangas
• 02:21   Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view Bruce Momjian
• 09:44   Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker Andrei Lepikhov
• 10:34   Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view Laurenz Albe
• 13:22   RE: Re:RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)
• 13:40   Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view Maxim Boguk
• 15:22   Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view Laurenz Albe
• 16:51   BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view Wetmore, Matthew (CTR)
• 17:08   Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view Tom Lane
• 18:07   Re:RE: Re:RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() ocean_li_996
• 22:04   BUG #18389: pg_database_owner not recognized with alter default privileges PG Bug reporting form
• 22:50   Re: A server crash with a SQL procedure returning a user-defined type on 14.8 Tom Lane
• 22:55   Re: BUG #18389: pg_database_owner not recognized with alter default privileges Noah Misch

13 March

• 01:08   Re: FSM Corruption (was: Could not read block at end of the relation) Noah Misch
• 05:57   BUG #18390: exponentiation produces float datatype, but nth-root produces integer PG Bug reporting form
• 06:24   RE: Re:RE: Re:RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)
• 06:33   Re: BUG #18369: logical decoding core on AssertTXNLsnOrder() feichanghong
• 07:39   RE: BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)
• 08:48   Re:RE: BUG #18369: logical decoding core on AssertTXNLsnOrder() ocean_li_996
• 09:50   Re: BUG #18385: Assert("strategy_delta >= 0") in BgBufferSync() fails due to race condition Tender Wang
• 10:16   AW: BUG #18389: pg_database_owner not recognized with alter default privileges Kristo Marijo
• 11:00   Re: BUG #18385: Assert("strategy_delta >= 0") in BgBufferSync() fails due to race condition Alexander Lakhin
• 11:44   Re: BUG #18389: pg_database_owner not recognized with alter default privileges Laurenz Albe
• 11:47   Re: BUG #18389: pg_database_owner not recognized with alter default privileges Kristo Marijo
• 12:07   Re: BUG #18389: pg_database_owner not recognized with alter default privileges Laurenz Albe
• 12:22   AW: BUG #18389: pg_database_owner not recognized with alter default privileges Kristo Marijo
• 12:34   RE: Potential data loss due to race condition during logical replication slot creation Hayato Kuroda (Fujitsu)
• 12:37   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 12:47   RE: Potential data loss due to race condition during logical replication slot creation Hayato Kuroda (Fujitsu)
• 12:54   RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)
• 14:18   BUG #18391: not able to create a new cluster using init db on rocky linux.We are forced to download version 1 3 PG Bug reporting form
• 15:07   Re: BUG #18390: exponentiation produces float datatype, but nth-root produces integer David G. Johnston
• 16:00   Re: BUG #18391: not able to create a new cluster using init db on rocky linux.We are forced to download version 1 3 Laurenz Albe
• 17:12   Re: BUG #18390: exponentiation produces float datatype, but nth-root produces integer Tom Lane
• 19:55   Re: FSM Corruption (was: Could not read block at end of the relation) Noah Misch
• 20:08   Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view Bruce Momjian
• 21:32   Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view Tom Lane

14 March

• 03:49   Re:Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() ocean_li_996
• 04:40   RE: Re:Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)
• 05:14   Re:RE: Re:Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() ocean_li_996
• 06:06   BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update PG Bug reporting form
• 08:58   Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update Laurenz Albe
• 09:03   Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update Carl Smith
• 09:21   BUG #18393: Bad multiple "inplace" insert into domain of complex type PG Bug reporting form
• 11:55   Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update Laurenz Albe
• 18:12   Re: BUG #18393: Bad multiple "inplace" insert into domain of complex type Tom Lane

15 March

• 00:49   Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update Tom Lane
• 01:00   BUG #18394: LISTEN error: could not access status of transaction PG Bug reporting form
• 05:36   Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view Bruce Momjian
• 09:23   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 10:40   BUG #18395: Checksum verification failed for: deb_postgis_3_4_pg16.app.zip PG Bug reporting form
• 11:05   Re: BUG #18385: Assert("strategy_delta >= 0") in BgBufferSync() fails due to race condition Tender Wang
• 11:48   Re: BUG #18385: Assert("strategy_delta >= 0") in BgBufferSync() fails due to race condition Tender Wang
• 12:54   Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue Arnd Baranowski
• 15:46   Re: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Amit Kapila

16 March

• 06:03   Re: FSM Corruption (was: Could not read block at end of the relation) Noah Misch
• 07:58   Re: FSM Corruption (was: Could not read block at end of the relation) Noah Misch
• 14:51   Re: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Amit Kapila
• 15:38   Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 17:24   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 17:29   ReplicationSlotRelease may set the statusFlags of other processes in PG14 feichanghong
• 18:55   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 20:55   Postgres jdbc driver inconsistent behaviour with double precession  Rahul Uniyal
• 22:49   Re: Regression tests fail with musl libc because libpq.so can't be loaded Andrew Dunstan
• 23:00   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 23:10   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 23:19   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 23:21   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 23:31   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 23:54   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro

17 March

• 10:00   BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index PG Bug reporting form
• 12:44   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 13:33   Re: Regression tests fail with musl libc because libpq.so can't be loaded Christophe Pettus
• 16:11   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 18:44   Re: Regression tests fail with musl libc because libpq.so can't be loaded Christophe Pettus
• 23:33   Re: Regression tests fail with musl libc because libpq.so can't be loaded Andrew Dunstan

18 March

• 00:05   Re: Regression tests fail with musl libc because libpq.so can't be loaded Christophe Pettus
• 02:20   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 09:35   Re: "unexpected duplicate for tablespace" problem in logical replication Michael Paquier
• 09:44   RE: Re:RE: Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() Hayato Kuroda (Fujitsu)
• 12:08   Re: Potential data loss due to race condition during logical replication slot creation Amit Kapila
• 12:18   Re: Potential data loss due to race condition during logical replication slot creation Amit Kapila
• 12:33   Re: Regression tests fail with musl libc because libpq.so can't be loaded Christophe Pettus
• 16:25   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 17:05   BUG #18398: Simplified SQL Query for Problem Diagnosis PG Bug reporting form
• 17:23   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 23:18   Re: Postgres jdbc driver inconsistent behaviour with double precession Dave Cramer

19 March

• 00:17   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 01:36   Re: Postgres jdbc driver inconsistent behaviour with double precession Dave Cramer
• 01:48   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 02:23   BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery PG Bug reporting form
• 05:16   RE: Potential data loss due to race condition during logical replication slot creation Hayato Kuroda (Fujitsu)
• 05:33   Re: Potential data loss due to race condition during logical replication slot creation Amit Kapila
• 05:58   Re:BUG #18369: logical decoding core on AssertTXNLsnOrder() ocean_li_996
• 06:57   Re: ReplicationSlotRelease may set the statusFlags of other processes in PG14 Michael Paquier
• 07:39   RE: Potential data loss due to race condition during logical replication slot creation Hayato Kuroda (Fujitsu)
• 12:52   Re: Postgres jdbc driver inconsistent behaviour with double precession Dave Cramer
• 14:39   Re: Postgres jdbc driver inconsistent behaviour with double precession Dave Cramer
• 15:07   Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index Tender Wang
• 15:33   Re: BUG #18377: Assert false in "partdesc->nparts >= pinfo->nparts", fileName="execPartition.c", lineNumber=1943 Alvaro Herrera
• 17:26   Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index Heikki Linnakangas
• 18:31   BUG #18400: logging_collector does not collect messages from postmaster PG Bug reporting form
• 18:47   Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery Tom Lane
• 19:42   Re: Potential data loss due to race condition during logical replication slot creation Masahiko Sawada
• 23:50   BUG #18401: Cannot install PG Bug reporting form

20 March

• 02:11   Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery Sawyer Knoblich
• 02:54   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 02:57   Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update Carl Smith
• 03:37   Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery Tom Lane
• 04:12   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 04:27   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 04:53   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 05:01   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 05:03   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 05:12   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 05:20   Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery Sawyer Knoblich
• 07:08   Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery David Rowley
• 07:39   Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery Tom Lane
• 07:39   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 08:00   Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index Alexander Lakhin
• 09:02   Re: Regression tests fail with musl libc because libpq.so can't be loaded Peter Eisentraut
• 09:22   Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index Tender Wang
• 09:37   Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery Sawyer Knoblich
• 10:16   Re: Regression tests fail with musl libc because libpq.so can't be loaded Andrew Dunstan
• 12:39   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 12:55   performance: `tuplehash_iterate` and `group by` question, very slow Mingjun Yang
• 13:24   Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum Alexander Korotkov
• 15:27   Re: BUG #18401: Cannot install Kritika Agarwal
• 16:35   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 16:37   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 17:24   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 17:28   Re: Regression tests fail with musl libc because libpq.so can't be loaded Laurenz Albe
• 17:29   BUG #18402: Attaching a new partition doesn't reuse the prebuilt index on said partition PG Bug reporting form
• 17:36   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 17:37   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 17:43   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 17:46   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 19:00   Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum Alexander Lakhin
• 20:00   Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum Alexander Korotkov
• 21:37   Re: Regression tests fail with musl libc because libpq.so can't be loaded Peter Eisentraut
• 22:10   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 22:18   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 22:29   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 22:35   BUG #18403: PL/pgSQL is reporting unexpected errors when processing DECLARE blocks with <> PG Bug reporting form
• 22:42   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 23:37   Re: BUG #18403: PL/pgSQL is reporting unexpected errors when processing DECLARE blocks with <> Pavel Stehule
• 23:47   BUG #18403: PL/pgSQL is reporting unexpected errors when processing DECLARE blocks with <> David G. Johnston
• 23:57   Re: BUG #18403: PL/pgSQL is reporting unexpected errors when processing DECLARE blocks with <> Pavel Stehule

21 March

• 00:02   Re: BUG #18403: PL/pgSQL is reporting unexpected errors when processing DECLARE blocks with <> Tom Lane
• 01:26   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 08:46   Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum Andrey M. Borodin
• 16:51   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 19:15   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Robert Haas
• 20:21   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Matthias van de Meent
• 20:25   Index plan returns different results to sequential scan John Burns
• 22:27   Re: Index plan returns different results to sequential scan Tomas Vondra
• 23:16   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 23:30   Re: Regression tests fail with musl libc because libpq.so can't be loaded walther@technowledgy.de

22 March

• 01:42   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 02:02   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 02:20   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 02:23   Re: Regression tests fail with musl libc because libpq.so can't be loaded Andrew Dunstan
• 02:30   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 02:58   Re: Index plan returns different results to sequential scan Tomas Vondra
• 03:07   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 03:08   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 03:19   Re: Regression tests fail with musl libc because libpq.so can't be loaded Andres Freund
• 04:21   Re: Index plan returns different results to sequential scan Tomas Vondra
• 04:40   Re: Index plan returns different results to sequential scan Peter Geoghegan
• 08:42   Re: Index plan returns different results to sequential scan John Burns
• 09:12   Re: Regression tests fail with musl libc because libpq.so can't be loaded Andrew Dunstan
• 09:15   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 10:02   Re: Regression tests fail with musl libc because libpq.so can't be loaded Andrew Dunstan
• 10:43   Re: Index plan returns different results to sequential scan Tomas Vondra
• 10:55   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 11:02   Re: Regression tests fail with musl libc because libpq.so can't be loaded Wolfgang Walther
• 11:12   Re: Regression tests fail with musl libc because libpq.so can't be loaded walther@technowledgy.de
• 11:28   Re: Index plan returns different results to sequential scan Tomas Vondra
• 11:33   Re: Regression tests fail with musl libc because libpq.so can't be loaded walther@technowledgy.de
• 11:55   Re: BUG #18305: Unexpected error: "WindowFunc not found in subplan target lists" triggered by subqueries Richard Guo
• 12:41   Re: Regression tests fail with musl libc because libpq.so can't be loaded walther@technowledgy.de
• 13:47   Re: BUG #18305: Unexpected error: "WindowFunc not found in subplan target lists" triggered by subqueries Richard Guo
• 15:10   Re: Regression tests fail with musl libc because libpq.so can't be loaded Andrew Dunstan
• 15:22   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Robert Haas
• 16:00   BUG #18404: Select from pg_stat_activity in a plpgsql block can lead to a global locking issue PG Bug reporting form
• 16:36   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 19:59   NEW.* and OLD.* inside trigger function don't seem to contain recently added columns Janne Annala
• 21:41   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Melanie Plageman
• 22:34   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Robert Haas
• 22:43   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Noah Misch
• 22:44   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian

23 March

• 03:39   Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum Alexander Korotkov
• 03:41   Re: NEW.* and OLD.* inside trigger function don't seem to contain recently added columns Tom Lane
• 05:24   Re: Index plan returns different results to sequential scan Peter Geoghegan
• 14:24   Re: Index plan returns different results to sequential scan Tomas Vondra
• 14:37   Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum Alexander Korotkov
• 21:09   BUG #18405: flaw in dump of inherited/dropped constraints PG Bug reporting form

25 March

• 11:15   Re: NEW.* and OLD.* inside trigger function don't seem to contain recently added columns Janne Annala
• 13:09   BUG #18406: Connection issue after upgrading to postgres16 PG Bug reporting form
• 17:50   BUG #18407: ALTER TABLE SET SCHEMA on foreign table with SERIAL column does not move sequence to new schema PG Bug reporting form
• 18:52   Unexpected Name Resolution Behavior with ORDER BY COLLATE Clause in PostgreSQL 16.2 Bender, Patrice
• 19:11   Re: BUG #18405: flaw in dump of inherited/dropped constraints Tom Lane
• 19:16   Re: BUG #18405: flaw in dump of inherited/dropped constraints Scott Ribe
• 19:17   Re: BUG #18407: ALTER TABLE SET SCHEMA on foreign table with SERIAL column does not move sequence to new schema Tom Lane
• 22:04   Re: Unexpected Name Resolution Behavior with ORDER BY COLLATE Clause in PostgreSQL 16.2 Tom Lane
• 22:18   Re: Unexpected Name Resolution Behavior with ORDER BY COLLATE Clause in PostgreSQL 16.2 Laurenz Albe
• 22:20   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro

26 March

• 00:58   Re: Regression tests fail with musl libc because libpq.so can't be loaded walther@technowledgy.de
• 01:35   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 01:46   Re: Regression tests fail with musl libc because libpq.so can't be loaded Peter Eisentraut
• 01:51   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 01:54   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 02:14   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 02:15   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 02:21   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 02:43   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 02:49   Re: Regression tests fail with musl libc because libpq.so can't be loaded Thomas Munro
• 03:04   BUG #18408: ERROR: could not load library PG Bug reporting form
• 03:14   Re: Regression tests fail with musl libc because libpq.so can't be loaded Andres Freund
• 03:53   Re: Regression tests fail with musl libc because libpq.so can't be loaded Bruce Momjian
• 05:36   RE: BUG #18386: Slow connection access after 'vacuum full pg_attribute' 1165125080
• 06:55   Re: BUG #18408: ERROR: could not load library Sandeep Thakkar
• 07:24   Walsender getting klilled, ERROR: out of memory in server logs Subhrajit Mutsuddi
• 08:59   Re: BUG #18407: ALTER TABLE SET SCHEMA on foreign table with SERIAL column does not move sequence to new schema Peter Eisentraut
• 10:19   Re: Regression tests fail with musl libc because libpq.so can't be loaded Peter Eisentraut
• 10:36   Re: Regression tests fail with musl libc because libpq.so can't be loaded walther@technowledgy.de
• 10:43   Re: Regression tests fail with musl libc because libpq.so can't be loaded walther@technowledgy.de
• 12:55   Re: BUG #18408: ERROR: could not load library Francisco Olarte
• 13:07   Re: BUG #18408: ERROR: could not load library Andrew Dunstan
• 13:42   Re: Walsender getting klilled, ERROR: out of memory in server logs Laurenz Albe
• 15:09   Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index Tender Wang
• 16:09   Re: BUG #18402: Attaching a new partition doesn't reuse the prebuilt index on said partition gparc@free.fr
• 17:35   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 18:45   Re: Regression tests fail with musl libc because libpq.so can't be loaded Tom Lane
• 21:18   Re: BUG #18402: Attaching a new partition doesn't reuse the prebuilt index on said partition Euler Taveira
• 22:29   Re: BUG #18407: ALTER TABLE SET SCHEMA on foreign table with SERIAL column does not move sequence to new schema Tom Lane
• 22:34   Re: BUG #18406: Connection issue after upgrading to postgres16 Dave Cramer

27 March

• 05:59   Re: BUG #18395: Checksum verification failed for: deb_postgis_3_4_pg16.app.zip Sandeep Thakkar
• 09:43   Re: MarkBufferDirty Assert held LW_EXCLUSIVE lock fail when ginFinishSplit feichanghong
• 09:53   Re: ReplicationSlotRelease may set the statusFlags of other processes in PG14 feichanghong
• 10:42   Re: BUG #18379: LDAP bind password exposed Andrew Dunstan
• 10:54   RE: Potential data loss due to race condition during logical replication slot creation Hayato Kuroda (Fujitsu)
• 11:25   BUG #18409: After my windows update, I can not run postgre 16 server PG Bug reporting form
• 11:26   Re: Potential data loss due to race condition during logical replication slot creation Masahiko Sawada
• 11:58   Re: BUG #18409: After my windows update, I can not run postgre 16 server Daniel Gustafsson
• 13:37   RE: Potential data loss due to race condition during logical replication slot creation Hayato Kuroda (Fujitsu)
• 15:42   BUG #18410: SQL Error [XX000]: ERROR: variable not found in subplan target list PG Bug reporting form
• 16:01   Re: BUG #18410: SQL Error [XX000]: ERROR: variable not found in subplan target list Laurenz Albe
• 17:17   RE: BUG #18410: SQL Error [XX000]: ERROR: variable not found in subplan target list Fernando Asulay
• 18:21   Re: BUG #18410: SQL Error [XX000]: ERROR: variable not found in subplan target list Tom Lane
• 20:32   BUG #18411: Unable to create database with owner on AWS RDS PG Bug reporting form
• 21:04   BUG #18412: could not send data to client: Broken pipe PG Bug reporting form

28 March

• 00:00   Re: BUG #18411: Unable to create database with owner on AWS RDS Tom Lane
• 04:25   Re: BUG #18411: Unable to create database with owner on AWS RDS Andrey Lizenko
• 04:45   Re: BUG #18411: Unable to create database with owner on AWS RDS David G. Johnston
• 08:20   Re: BUG #18411: Unable to create database with owner on AWS RDS Andrey Lizenko
• 08:31   Re: BUG #18411: Unable to create database with owner on AWS RDS David G. Johnston
• 15:51   BUG #18414: When the key values are the same, the memory limit is exceeded when making a hash join PG Bug reporting form
• 19:16   BUG #18415: Logical replication errors. PG Bug reporting form
• 20:02   Re: BUG #18415: Logical replication errors. David G. Johnston

29 March

• 02:27   BUG #18416: Confirmation of Issue with PostgreSQL ODBC Driver for Windows PG Bug reporting form
• 05:03   Re: BUG #18405: flaw in dump of inherited/dropped constraints Scott Ribe
• 07:44   BUG #18417: Excessive log messages on warm standby server PG Bug reporting form
• 11:47   Re: FSM Corruption (was: Could not read block at end of the relation) Ronan Dunklau
• 11:57   Re: BUG #18416: Confirmation of Issue with PostgreSQL ODBC Driver for Windows Laurenz Albe
• 15:19   Re: BUG #18415: Logical replication errors. vignesh C
• 19:05   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Robert Haas
• 20:16   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Peter Geoghegan
• 21:27   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Robert Haas

30 March

• 19:19   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Melanie Plageman
• 20:35   Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Robert Haas