pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Issue with PostgreSQL 18.0 Docker image volume mount (/var/lib/postgresql/data symlink)
  2025-09-26 05:53 UTC  Pavel Hushcha <paul.fastest@gmail.com>
` Re: Issue with PostgreSQL 18.0 Docker image volume mount (/var/lib/postgresql/data symlink)
  2025-09-26 09:14 UTC  Magnus Hagander <magnus@hagander.net>
  [2+ messages in thread]

BUG #19058: Empty repomd.xml.asc file
  2025-09-19 11:49 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19058: Empty repomd.xml.asc file
  2025-09-25 10:54 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

BUG #19063: Heavily nesting trivial ROW projections produces out of memory error
  2025-09-24 14:06 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19063: Heavily nesting trivial ROW projections produces out of memory error
  2025-09-24 18:43 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19063: Heavily nesting trivial ROW projections produces out of memory error
  2025-09-25 08:30 UTC  Lukas Eder <lukas.eder@gmail.com>
  [3+ messages in thread]

=?gb18030?B?u9i4tKO6IFRoZSBpc3N1ZSBvZiBpbmNvcnJlY3Qg?= =?gb18030?B?d2lkdGggZXN0aW1hdGlvbiBpbiBVTklPTiBxdWVy?= =?gb18030?B?aWVz?=
  2025-09-24 11:27 UTC  =?gb18030?B?V2VpIFN1bg==?= <936739278@qq.com>

Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-08-11 06:20 UTC  Zane Duffield <duffieldzane@gmail.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-08-11 10:55 UTC  Amit Kapila <amit.kapila16@gmail.com>
` RE: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-08-11 11:27 UTC  Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` RE: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-08-18 11:48 UTC  Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` RE: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-08-18 11:51 UTC  Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-08-20 05:38 UTC  Zane Duffield <duffieldzane@gmail.com>
` RE: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-08-20 09:58 UTC  Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-08-21 04:26 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-09-18 04:17 UTC  Zane Duffield <duffieldzane@gmail.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-09-22 08:36 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
  2025-09-24 08:34 UTC  Amit Kapila <amit.kapila16@gmail.com>
  [11+ messages in thread]

BUG #19061: I downloaded version 17 of postgreSQL and it was lagging very much
  2025-09-23 16:17 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19061: I downloaded version 17 of postgreSQL and it was lagging very much
  2025-09-24 05:21 UTC  David Rowley <dgrowleyml@gmail.com>
  [2+ messages in thread]

Numeric Type Precision Not Respected in Function or Procedure Arguments
  2025-09-22 19:39 UTC  Aaron Ackerman <aackerman@goodmorning.com>
` Re: Numeric Type Precision Not Respected in Function or Procedure Arguments
  2025-09-22 21:31 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Numeric Type Precision Not Respected in Function or Procedure Arguments
  2025-09-22 21:33 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [3+ messages in thread]

Maybe problems with autovaccum?
  2025-09-22 12:06 UTC  Franz Philipp Moser <fpmedv@gmail.com>

regexp_replace not respecting greediness
  2025-09-19 12:36 UTC  Simon Ellmann <simon.ellmann@tum.de>
` Re: regexp_replace not respecting greediness
  2025-09-19 14:09 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: regexp_replace not respecting greediness
  2025-09-19 16:01 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: regexp_replace not respecting greediness
  2025-09-22 08:07 UTC  Simon Ellmann <simon.ellmann@tum.de>
  [4+ messages in thread]

coredump of language internal function
  2025-09-22 04:56 UTC  myzhen <zhenmingyang@yeah.net>
` Re: coredump of language internal function
  2025-09-22 05:05 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
  2025-09-20 16:08 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
  2025-09-20 21:19 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
  2025-09-20 22:54 UTC  Christophe Pettus <xof@thebuild.com>
` Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
  2025-09-20 23:19 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
  2025-09-21 09:09 UTC  Vik Fearing <vik@postgresfriends.org>
` Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
  2025-09-21 16:05 UTC  =?utf-8?B?SmluaHVpIExhaQ==?= <jinhui.lai@qq.com>
  [6+ messages in thread]

BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-17 15:08 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-17 21:43 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-17 22:32 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 01:33 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 01:58 UTC  feichanghong <feichanghong@qq.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 03:10 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 03:37 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 03:47 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 04:11 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 04:19 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 04:29 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 04:38 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 04:56 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 05:15 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 06:09 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 06:15 UTC  feichanghong <feichanghong@qq.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 06:20 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 07:05 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-18 08:25 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-19 02:05 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
  2025-09-19 02:42 UTC  Amit Langote <amitlangote09@gmail.com>
  [21+ messages in thread]

BUG #19057: Installing postgresql-15 from the repostory installs a mix of postgresql 15 and 17
  2025-09-18 21:24 UTC  PG Bug reporting form <noreply@postgresql.org>

"unexpected duplicate for tablespace" problem in logical replication
  2022-04-06 02:14 UTC  wangsh.fnst@fujitsu.com <wangsh.fnst@fujitsu.com>
` RE: "unexpected duplicate for tablespace" problem in logical replication
  2022-04-08 09:44 UTC  osumi.takamichi@fujitsu.com <osumi.takamichi@fujitsu.com>
` RE: "unexpected duplicate for tablespace" problem in logical replication
  2022-04-11 07:40 UTC  osumi.takamichi@fujitsu.com <osumi.takamichi@fujitsu.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2022-04-11 10:24 UTC  wangsh.fnst@fujitsu.com <wangsh.fnst@fujitsu.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2022-04-12 02:45 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2022-04-12 03:36 UTC  wangsh.fnst@fujitsu.com <wangsh.fnst@fujitsu.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2022-04-19 06:23 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2024-01-08 05:02 UTC  vignesh C <vignesh21@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2024-01-12 08:37 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2024-01-15 21:32 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2024-01-16 01:58 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2024-02-02 15:49 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2024-03-18 06:35 UTC  Michael Paquier <michael@paquier.xyz>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2024-07-24 21:51 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-03-25 10:01 UTC  vignesh C <vignesh21@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-06-19 08:47 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-08-13 09:48 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-08-13 09:59 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-08-21 06:12 UTC  Michael Paquier <michael@paquier.xyz>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-08-21 14:24 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-08-21 21:36 UTC  Michael Paquier <michael@paquier.xyz>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-09-18 12:07 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-09-18 12:17 UTC  Andres Freund <andres@anarazel.de>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-09-18 12:22 UTC  Andres Freund <andres@anarazel.de>
` Re: "unexpected duplicate for tablespace" problem in logical replication
  2025-09-18 15:30 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
  [25+ messages in thread]

Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary
  2025-09-16 22:52 UTC  Nazneen Jafri <jafrinazneen@gmail.com>
` Re: Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary
  2025-09-16 23:42 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary
  2025-09-17 02:45 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary
  2025-09-17 04:05 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary
  2025-09-17 04:23 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary
  2025-09-17 04:32 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary
  2025-09-17 16:00 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary
  2025-09-17 22:34 UTC  Euler Taveira <euler@eulerto.com>
  [8+ messages in thread]

BUG #19055: Server crash at ExecInterpExpr
  2025-09-17 14:34 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19055: Server crash at ExecInterpExpr
  2025-09-17 17:57 UTC  Vik Fearing <vik@postgresfriends.org>
` Re: BUG #19055: Server crash at ExecInterpExpr
  2025-09-17 18:02 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #15986: Hhhhhhh
  2019-08-30 20:08 UTC  PG Bug reporting form <noreply@postgresql.org>
` [PATCH v1 1/1] max_active_replication_origins fix
  2025-09-17 02:56 UTC  Nathan Bossart <nathan@postgresql.org>
  [2+ messages in thread]

BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-10 07:14 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-10 11:36 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-10 12:30 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-10 13:29 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-11 01:40 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-11 03:10 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-11 03:16 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-12 00:57 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-16 01:05 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-16 10:18 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19046: Incorrect result when using json_array() with column reference in subquery combined with RIGHT JOIN
  2025-09-16 10:31 UTC  Tender Wang <tndrwang@gmail.com>
  [11+ messages in thread]

BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-13 14:10 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-18 10:29 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-18 13:46 UTC  Phineas Jensen <phin@zayda.net>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-18 15:21 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-18 16:46 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXTERNAL] Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-19 15:37 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-19 15:53 UTC  Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-19 16:04 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-19 16:57 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-19 20:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-20 11:29 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-06-20 17:50 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-08-29 15:55 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-09-15 14:46 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-09-15 16:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-09-15 18:23 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-09-15 20:06 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
  2025-09-16 02:08 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [18+ messages in thread]

BUG #19052: failing to install on Windows if user path contains Chineese/Korean characters
  2025-09-15 09:10 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19052: failing to install on Windows if user path contains Chineese/Korean characters
  2025-09-15 23:19 UTC  Thomas Munro <thomas.munro@gmail.com>
  [2+ messages in thread]

BUG #19054: Memory exhaustion vulnerability in PostgreSQL array operations leads to server crash
  2025-09-15 20:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19054: Memory exhaustion vulnerability in PostgreSQL array operations leads to server crash
  2025-09-15 20:30 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [2+ messages in thread]

BUG #19053: Inconsistent arithmetic regarding TIMESTAMPTZ and INTERVAL
  2025-09-15 10:12 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19053: Inconsistent arithmetic regarding TIMESTAMPTZ and INTERVAL
  2025-09-15 15:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re:BUG #19053: Inconsistent arithmetic regarding TIMESTAMPTZ and INTERVAL
  2025-09-15 16:03 UTC  ocean_li_996 <ocean_li_996@163.com>
` Re: BUG #19053: Inconsistent arithmetic regarding TIMESTAMPTZ and INTERVAL
  2025-09-15 17:24 UTC  Jan Behrens <jbe-mlist@magnetkern.de>
  [4+ messages in thread]

Version 17.6 changed how similar works compared to version 17.5
  2025-09-12 13:45 UTC  Stephan Springl <springl-psql@bfw-online.de>
` Re: Version 17.6 changed how similar works compared to version 17.5
  2025-09-12 23:41 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Version 17.6 changed how similar works compared to version 17.5
  2025-09-14 10:43 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [3+ messages in thread]

BUG #19051: Is it possible to move a TOAST table to a different tablespace than its parent table?
  2025-09-14 09:17 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19051: Is it possible to move a TOAST table to a different tablespace than its parent table?
  2025-09-14 10:29 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [2+ messages in thread]

BUG #19050: psql: could not find digest for NID UNDEF
  2025-09-11 13:23 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19050: psql: could not find digest for NID UNDEF
  2025-09-11 15:00 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19050: psql: could not find digest for NID UNDEF
  2025-09-13 12:23 UTC  TKP <tommi.pakarinen@gmail.com>
  [3+ 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