pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #18129: GiST index produces incorrect query results
  2023-09-22 06:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18129: GiST index produces incorrect query results
  2023-09-22 13:43 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18129: GiST index produces incorrect query results
  2023-09-23 22:06 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18129: GiST index produces incorrect query results
  2023-09-25 21:24 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18129: GiST index produces incorrect query results
  2023-09-26 08:08 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18129: GiST index produces incorrect query results
  2023-10-02 11:28 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
  [6+ messages in thread]

BUG #18135: Incorrect memory access occurs when attaching a partition with an index
  2023-09-27 10:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
  2023-09-28 03:30 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
  2023-09-28 05:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
  2023-09-28 07:07 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
  2023-09-28 08:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
  2023-09-28 17:31 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
  2023-10-01 00:31 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
  2023-10-01 00:39 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
  2023-10-02 02:56 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
  2023-10-02 03:04 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [10+ messages in thread]

BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
  2023-09-26 01:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
  2023-09-27 10:00 UTC  Japin Li <japinli@hotmail.com>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
  2023-09-30 06:36 UTC  Jov <amutu@amutu.com>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
  2023-09-30 23:48 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
  2023-10-01 00:44 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
  2023-10-01 00:54 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
  2023-10-01 00:58 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
  2023-10-02 02:27 UTC  Michael Paquier <michael@paquier.xyz>
  [8+ messages in thread]

BUG #18141: sorry, too many clients error occurring very frequently
  2023-09-29 14:31 UTC  PG Bug reporting form <noreply@postgresql.org>
` BUG #18141: sorry, too many clients error occurring very frequently
  2023-09-29 18:12 UTC  Wetmore, Matthew (CTR) <Matthew.Wetmore@express-scripts.com>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
  2023-09-29 18:12 UTC  Joe Conway <mail@joeconway.com>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
  2023-09-30 18:04 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
  2023-10-01 14:34 UTC  Joe Conway <mail@joeconway.com>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
  2023-10-01 18:09 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
  2023-10-01 18:27 UTC  Joe Conway <mail@joeconway.com>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
  2023-10-01 19:45 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [8+ messages in thread]

Help pg_restore version
  2023-09-30 10:33 UTC  Jorge Soro Domenech <jorsodom@gmail.com>
` Re: Help pg_restore version
  2023-10-01 13:29 UTC  Euler Taveira <euler@eulerto.com>
` Re: Help pg_restore version
  2023-10-01 15:28 UTC  Jorge Soro Domenech <jorsodom@gmail.com>
` Re: Help pg_restore version
  2023-10-01 15:34 UTC  Jorge Soro Domenech <jorsodom@gmail.com>
` Re: Help pg_restore version
  2023-10-01 16:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Help pg_restore version
  2023-10-01 16:39 UTC  Jorge Soro Domenech <jorsodom@gmail.com>
  [6+ messages in thread]

Bug in postgresql related column level security authentication.
  2023-10-01 07:59 UTC  Shubham Gholap <shubhamgholap2910@gmail.com>
` Re: Bug in postgresql related column level security authentication.
  2023-10-01 16:21 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."
  2023-09-28 07:24 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."
  2023-09-29 18:15 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."
  2023-09-29 18:17 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."
  2023-09-29 18:32 UTC  Bruce Momjian <bruce@momjian.us>
  [4+ messages in thread]

Broken type checking for empty subqueries
  2023-09-28 09:08 UTC  Marek Malevič <marek@malevicovi.net>
` Re: Broken type checking for empty subqueries
  2023-09-28 11:28 UTC  Vik Fearing <vik@postgresfriends.org>
` Re: Broken type checking for empty subqueries
  2023-09-28 12:41 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Broken type checking for empty subqueries
  2023-09-28 14:47 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Broken type checking for empty subqueries
  2023-09-28 14:57 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Broken type checking for empty subqueries
  2023-09-28 21:10 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Broken type checking for empty subqueries
  2023-09-28 21:53 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Broken type checking for empty subqueries
  2023-09-29 07:52 UTC  David Rowley <dgrowleyml@gmail.com>
  [8+ messages in thread]

md5 password valid and invalid after upgrading
  2023-09-26 23:14 UTC  Kyle MacMillan <macattackftw@gmail.com>
` Re: md5 password valid and invalid after upgrading
  2023-09-27 08:04 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: md5 password valid and invalid after upgrading
  2023-09-27 19:26 UTC  Kyle MacMillan <macattackftw@gmail.com>
` Re: md5 password valid and invalid after upgrading
  2023-09-27 22:25 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: md5 password valid and invalid after upgrading
  2023-09-28 21:49 UTC  Kyle MacMillan <macattackftw@gmail.com>
` Re: md5 password valid and invalid after upgrading
  2023-09-28 22:14 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: md5 password valid and invalid after upgrading
  2023-09-28 23:32 UTC  Kyle MacMillan <macattackftw@gmail.com>
  [7+ messages in thread]

BUG #18139: Causing FATAL error on database using function last() or first()
  2023-09-28 17:02 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18139: Causing FATAL error on database using function last() or first()
  2023-09-28 18:50 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18139: Causing FATAL error on database using function last() or first()
  2023-09-28 19:36 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [3+ messages in thread]

BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX  CONCURRENTLY when blocksize=1
  2023-09-21 11:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX CONCURRENTLY when blocksize=1
  2023-09-22 12:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX CONCURRENTLY when blocksize=1
  2023-09-28 07:16 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX  CONCURRENTLY when blocksize=1
  2023-09-28 16:25 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX CONCURRENTLY when blocksize=1
  2023-09-28 16:31 UTC  Andres Freund <andres@anarazel.de>
  [5+ messages in thread]

BUG #18138: Using limit on VALUES causes type conversion to fail.
  2023-09-28 12:44 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18138: Using limit on VALUES causes type conversion to fail.
  2023-09-28 14:47 UTC  Pantelis Theodosiou <ypercube@gmail.com>
` Re: BUG #18138: Using limit on VALUES causes type conversion to fail.
  2023-09-28 15:04 UTC  Akash Kava <ackava@gmail.com>
` Re: BUG #18138: Using limit on VALUES causes type conversion to fail.
  2023-09-28 15:57 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

Missed TidRangePath in the print_path switch
  2023-09-28 05:07 UTC  Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: Missed TidRangePath in the print_path switch
  2023-09-28 10:33 UTC  David Rowley <dgrowleyml@gmail.com>
  [2+ messages in thread]

回复: Bug of psql meta-command \sf & \sv
  2023-09-28 02:09 UTC  咸�9�5 <2437705447@qq.com>

BUG #18136: lc_messages is the empty string but should be 'C'?
  2023-09-27 15:04 UTC  PG Bug reporting form <noreply@postgresql.org>

Bug of psql meta-command \sf & \sv
  2023-09-27 09:06 UTC  Jet Zhang <jet.cx.zhang@hotmail.com>
` Re: Bug of psql meta-command \sf & \sv
  2023-09-27 09:13 UTC  Daniel Gustafsson <daniel@yesql.se>
` RE: Bug of psql meta-command \sf & \sv
  2023-09-27 09:25 UTC  Jet Zhang <jet.cx.zhang@hotmail.com>
` Re: Bug of psql meta-command \sf & \sv
  2023-09-27 10:33 UTC  Japin Li <japinli@hotmail.com>
` RE: Bug of psql meta-command \sf & \sv
  2023-09-27 11:03 UTC  Jet Zhang <jet.cx.zhang@hotmail.com>
` Re: Bug of psql meta-command \sf & \sv
  2023-09-27 12:35 UTC  咸�9�5 <2437705447@qq.com>
` Re: Bug of psql meta-command \sf & \sv
  2023-09-27 14:16 UTC  Japin Li <japinli@hotmail.com>
  [7+ messages in thread]

PG_DUMPALL not executable within docker container
  2023-09-27 08:43 UTC  Patrick Frießnegg <patrick.fri@gmail.com>
` Re: PG_DUMPALL not executable within docker container
  2023-09-27 09:06 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: PG_DUMPALL not executable within docker container
  2023-09-27 09:47 UTC  Patrick Frießnegg <patrick.fri@gmail.com>
  [3+ messages in thread]

PostgreSQL's processes blocking each other are not detected as deadlock
  2023-09-26 10:23 UTC  Sorin Mircioiu <sorin.mircioiu@gmail.com>
` Re: PostgreSQL's processes blocking each other are not detected as deadlock
  2023-09-26 14:02 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL's processes blocking each other are not detected as deadlock
  2023-09-27 08:32 UTC  Sorin Mircioiu <sorin.mircioiu@gmail.com>
  [3+ messages in thread]

BUG #18103: bugs of concurrent merge into when use different join plan
  2023-09-10 12:57 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18103: bugs of concurrent merge into when use different join plan
  2023-09-14 07:29 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18103: bugs of concurrent merge into when use different join plan
  2023-09-18 06:44 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18103: bugs of concurrent merge into when use different join plan
  2023-09-21 11:49 UTC  Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18103: bugs of concurrent merge into when use different join plan
  2023-09-26 09:46 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18103: bugs of concurrent merge into when use different join plan
  2023-09-27 07:29 UTC  Dean Rasheed <dean.a.rasheed@gmail.com>
  [6+ messages in thread]

BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
  2023-09-21 06:39 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
  2023-09-22 01:47 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
  2023-09-22 01:55 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
  2023-09-22 02:06 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
  2023-09-22 02:07 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
  2023-09-22 02:08 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
  2023-09-25 17:45 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
  2023-09-25 22:32 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
  2023-09-26 16:09 UTC  Bruce Momjian <bruce@momjian.us>
  [9+ messages in thread]

BUG #17928: Standby fails to decode WAL on termination of primary
  2023-05-11 08:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-05-11 18:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-05-15 03:38 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-07-10 20:00 UTC  Noah Misch <noah@leadboat.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-07-11 06:54 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-07-17 00:49 UTC  Noah Misch <noah@leadboat.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-07-20 06:01 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-10 07:45 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-10 23:22 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-11 02:58 UTC  Noah Misch <noah@leadboat.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-11 06:08 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-11 14:00 UTC  Noah Misch <noah@leadboat.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-11 23:56 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-12 00:20 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-12 00:32 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-12 21:13 UTC  Noah Misch <noah@leadboat.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-13 03:12 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-13 03:30 UTC  Noah Misch <noah@leadboat.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-14 02:08 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-14 03:56 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-14 10:28 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-15 02:04 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-15 02:36 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-15 03:00 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-15 06:11 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-16 03:29 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-16 06:17 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-18 00:20 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-18 02:30 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-18 04:55 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-08-20 23:32 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-02 01:29 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-02 11:51 UTC  Sergei Kornilov <sk@zsrv.org>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-02 23:42 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-03 05:43 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-03 11:21 UTC  Sergei Kornilov <sk@zsrv.org>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-04 03:20 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-04 03:54 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-04 07:17 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-04 07:28 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-04 07:43 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-05 03:19 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-05 03:58 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-05 04:13 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-12 01:01 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-12 02:08 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-12 02:12 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-15 22:07 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-16 00:02 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-16 00:20 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-16 04:13 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-16 06:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-17 20:46 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-19 09:25 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-19 09:53 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-19 10:09 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-19 13:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-19 22:51 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-20 00:51 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-20 06:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-22 03:11 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-22 04:02 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-22 23:35 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-23 00:05 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-23 00:16 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-23 00:20 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-23 01:07 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-23 02:02 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-23 02:29 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-23 04:44 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-23 20:48 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-23 23:23 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-24 20:02 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-24 23:58 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 00:18 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 01:32 UTC  Noah Misch <noah@leadboat.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 03:07 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 03:29 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 03:47 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 04:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 05:05 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 05:13 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 05:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 06:52 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-25 22:14 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17928: Standby fails to decode WAL on termination of primary
  2023-09-26 00:34 UTC  Michael Paquier <michael@paquier.xyz>
  [86+ messages in thread]

Re: BUG #18133: Canceling statement due to statement timeout
  2023-09-25 10:31 UTC  SOzcn <selahattinozcnma@gmail.com>
` Re: BUG #18133: Canceling statement due to statement timeout
  2023-09-25 15:49 UTC  Greg Sabino Mullane <htamfids@gmail.com>
  [2+ messages in thread]

BUG #18132: llvm-jit does not build with LLVM 17
  2023-09-23 20:43 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18132: llvm-jit does not build with LLVM 17
  2023-09-24 20:43 UTC  Thomas Munro <thomas.munro@gmail.com>
  [2+ messages in thread]

BUG #18131: PL/pgSQL: regclass procedure parameter wrongly memoized(?)
  2023-09-22 19:22 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18131: PL/pgSQL: regclass procedure parameter wrongly memoized(?)
  2023-09-22 21:32 UTC  Christian Stork <cstork+postgresql@gmail.com>
` Re: BUG #18131: PL/pgSQL: regclass procedure parameter wrongly memoized(?)
  2023-09-23 16:39 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

why are null bytes allowed in JSON columns?
  2023-09-22 01:40 UTC  Wyatt Alt <wyatt.alt@gmail.com>
` Re: why are null bytes allowed in JSON columns?
  2023-09-22 01:53 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: why are null bytes allowed in JSON columns?
  2023-09-22 01:57 UTC  Wyatt Alt <wyatt.alt@gmail.com>
` Re: why are null bytes allowed in JSON columns?
  2023-09-22 21:37 UTC  Andrew Dunstan <andrew@dunslane.net>
  [4+ messages in thread]


[next (older)]

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox