pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-29 20:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 04:07 UTC  jian he <jian.universality@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 04:41 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 04:52 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 05:08 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 05:31 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 06:44 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 08:29 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 08:55 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 09:17 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 09:53 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 11:08 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 13:17 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 13:31 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-30 13:48 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-31 00:30 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-10-31 01:50 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-06 10:00 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-07 01:01 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-07 06:02 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-07 06:03 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-07 06:35 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-07 09:04 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-07 09:23 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-08 05:19 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-26 11:27 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-27 01:25 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2025-11-30 05:59 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2026-01-14 12:30 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2026-01-14 13:38 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2026-01-16 07:57 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2026-01-19 17:56 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2026-01-19 18:25 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2026-01-20 03:07 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2026-01-21 12:58 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
  2026-01-23 01:40 UTC  Amit Langote <amitlangote09@gmail.com>
  [36+ messages in thread]

BUG #19385: Normal SELECT generates an ineffecifient query plan compare to the prepared SELECT.
  2026-01-21 06:53 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19385: Normal SELECT generates an ineffecifient query plan compare to the prepared SELECT.
  2026-01-21 11:57 UTC  Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19385: Normal SELECT generates an ineffecifient query plan compare to the prepared SELECT.
  2026-01-21 15:30 UTC  Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19385: Normal SELECT generates an ineffecifient query plan compare to the prepared SELECT.
  2026-01-22 01:31 UTC  David Rowley <dgrowleyml@gmail.com>
  [4+ messages in thread]

BUG #19377: Query planner interesting behaviour
  2026-01-13 06:15 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19377: Query planner interesting behaviour
  2026-01-21 08:06 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19377: Query planner interesting behaviour
  2026-01-21 16:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #19386: Unnecessary Sort in query plan for SELECT literal with ORDER BY
  2026-01-21 08:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19386: Unnecessary Sort in query plan for SELECT literal with ORDER BY
  2026-01-21 11:11 UTC  Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19386: Unnecessary Sort in query plan for SELECT literal with ORDER BY
  2026-01-21 11:42 UTC  Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19386: Unnecessary Sort in query plan for SELECT literal with ORDER BY
  2026-01-21 15:42 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

Resolved!
  2026-01-20 15:16 UTC  Anatol V <vershilovich@gmail.com>

BUG #19383: Server crash at getmissingattr
  2026-01-20 05:08 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19383: Server crash at getmissingattr
  2026-01-20 09:15 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19383: Server crash at getmissingattr
  2026-01-20 15:10 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG: psql 18.1 Windows Installer - Readline/libedit support missing in psql.exe.
  2026-01-19 14:40 UTC  MichaelDBA <MichaelDBA@sqlexec.com>

BUG #19373: One backend hanging in AioIoUringExecution blocking other backends
  2026-01-09 10:14 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19373: One backend hanging in AioIoUringExecution blocking other backends
  2026-01-17 00:09 UTC  surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19373: One backend hanging in AioIoUringExecution blocking other backends
  2026-01-17 09:03 UTC  Michael Kröll <michael.kroell@gmail.com>
  [3+ messages in thread]

BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2025-12-15 01:40 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2025-12-15 06:25 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2025-12-22 14:51 UTC  Bh W <wangbihua.cn@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2025-12-22 22:37 UTC  Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2025-12-24 08:08 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2025-12-24 12:07 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2025-12-24 23:11 UTC  Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2025-12-25 04:48 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2025-12-31 16:16 UTC  Bernice Southey <bernice.southey@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2026-01-01 21:58 UTC  Bernice Southey <bernice.southey@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2026-01-07 09:37 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2026-01-07 09:45 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2026-01-07 11:18 UTC  Bernice Southey <bernice.southey@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2026-01-07 12:16 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2026-01-07 12:52 UTC  Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2026-01-08 13:16 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2026-01-15 11:39 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2026-01-15 16:34 UTC  Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
  2026-01-16 06:23 UTC  Amit Langote <amitlangote09@gmail.com>
  [19+ messages in thread]

 Re[2]: BUG #19379: Role pg_read_all_data don't allowed read large objects
  2026-01-15 14:05 UTC  Глеб Борков <long76.git@mail.ru>

uninitialized var in encnames.c
  2026-01-15 08:00 UTC  ma lz <ma100@hotmail.com>
` 回复: uninitialized var in encnames.c 
  2026-01-15 08:06 UTC  ma lz <ma100@hotmail.com>
  [2+ messages in thread]

BUG #19378: How do you know to start Postgresql with "systemctl start postgresql@18-main" ?
  2026-01-14 19:28 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19366: heap-use-after-free in pgaio_io_reclaim() detected with RELCACHE_FORCE_RELEASE
  2025-12-29 06:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19366: heap-use-after-free in pgaio_io_reclaim() detected with RELCACHE_FORCE_RELEASE
  2026-01-14 16:45 UTC  Andres Freund <andres@anarazel.de>
  [2+ messages in thread]

Inconsistent handling of signed zero (-0) between INNER JOIN and INTERSECT ALL
  2026-01-12 16:25 UTC  =?utf-8?B?5byA5b+D5bCP5biC5rCR?= <2530254482@qq.com>
` Re: Inconsistent handling of signed zero (-0) between INNER JOIN and INTERSECT ALL
  2026-01-12 19:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #19375: PathTarget expression costs are being double-counted in the planner
  2026-01-12 12:16 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently
  2025-12-27 23:57 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently
  2025-12-29 17:28 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently
  2026-01-09 16:19 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently
  2026-01-09 22:56 UTC  Paveł Tyślacki <pavel.tyslacki@gmail.com>
  [4+ messages in thread]

Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
  2026-01-06 13:58 UTC  Andrii <andriikrivich@gmail.com>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
  2026-01-07 16:32 UTC  Andres Freund <andres@anarazel.de>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
  2026-01-07 16:33 UTC  Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
  2026-01-07 21:08 UTC  Andrii <andriikrivich@gmail.com>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
  2026-01-07 21:14 UTC  Andres Freund <andres@anarazel.de>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
  2026-01-08 04:45 UTC  Gilles Darold <gilles@darold.net>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
  2026-01-08 11:36 UTC  Andrii <andriikrivich@gmail.com>
  [7+ messages in thread]

BUG #19372: Scan operator maybe output unnecessary columns to the upper-layer operators
  2026-01-07 08:11 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19372: Scan operator maybe output unnecessary columns to the upper-layer operators
  2026-01-07 09:25 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19372: Scan operator maybe output unnecessary columns to the upper-layer operators
  2026-01-08 03:02 UTC  David Rowley <dgrowleyml@gmail.com>
  [3+ messages in thread]

BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
  2026-01-06 05:32 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
  2026-01-06 09:26 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
  2026-01-06 15:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
  2026-01-06 16:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
  2026-01-06 16:45 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
  2026-01-06 17:42 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
  2026-01-06 18:35 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
  2026-01-06 19:01 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
  2026-01-07 01:04 UTC  Andres Freund <andres@anarazel.de>
  [9+ messages in thread]

BUG #19371: programı yüklerken hata veriyor
  2026-01-06 05:57 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
  2025-12-12 10:11 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
  2025-12-12 16:54 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
  2025-12-13 10:01 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
  2025-12-15 14:28 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
  2025-12-16 11:30 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
  2025-12-24 02:15 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
  2025-12-24 02:40 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
  2025-12-25 03:58 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
  2026-01-05 08:31 UTC  Marian Muller Rebeyrol <marian.muller@serli.com>
  [9+ messages in thread]

BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-29 09:54 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-29 11:31 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-29 12:43 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-29 13:52 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-29 15:03 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-29 15:07 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-29 15:30 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-29 18:51 UTC  Paul A Jungwirth <pj@illuminatedcomputing.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-30 10:30 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-30 17:20 UTC  Paul A Jungwirth <pj@illuminatedcomputing.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-30 18:31 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-31 08:51 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-31 09:11 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-10-31 11:22 UTC  Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2025-12-31 22:47 UTC  Paul A Jungwirth <pj@illuminatedcomputing.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  2026-01-02 18:32 UTC  Paul A Jungwirth <pj@illuminatedcomputing.com>
  [16+ messages in thread]

BUG #19368: f54af9f does not create the correct macro for autotools build
  2025-12-31 00:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19368: f54af9f does not create the correct macro for autotools build
  2025-12-31 15:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19368: f54af9f does not create the correct macro for autotools build
  2025-12-31 16:50 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #19368: f54af9f does not create the correct macro for autotools build
  2025-12-31 16:52 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19368: f54af9f does not create the correct macro for autotools build
  2025-12-31 19:20 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #19368: f54af9f does not create the correct macro for autotools build
  2026-01-02 14:28 UTC  Andres Freund <andres@anarazel.de>
  [6+ messages in thread]

 GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-11-17 08:02 UTC  Haowu Ge <gehaowu@bitmoe.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-11-18 08:27 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-11-19 10:07 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-08 06:10 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-09 06:38 UTC  Richard Guo <guofenglinux@gmail.com>
`  Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-09 08:54 UTC  Haowu Ge <gehaowu@bitmoe.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-10 02:01 UTC  Richard Guo <guofenglinux@gmail.com>
`  Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-11 02:32 UTC  Haowu Ge <gehaowu@bitmoe.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-12 09:28 UTC  Richard Guo <guofenglinux@gmail.com>
`  Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-15 01:23 UTC  Haowu Ge <gehaowu@bitmoe.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-18 08:56 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-24 07:50 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-24 10:05 UTC  Haowu Ge <gehaowu@bitmoe.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-28 04:20 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-28 16:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
  2025-12-30 03:47 UTC  Richard Guo <guofenglinux@gmail.com>
  [16+ messages in thread]

BUG #19367: typos in backend/utils/adt/timestamp.c
  2025-12-29 09:13 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19367: typos in backend/utils/adt/timestamp.c
  2025-12-29 10:25 UTC  Rahila Syed <rahilasyed90@gmail.com>
` Re: BUG #19367: typos in backend/utils/adt/timestamp.c
  2025-12-29 10:35 UTC  Japin Li <japinli@hotmail.com>
` RE: BUG #19367: typos in backend/utils/adt/timestamp.c
  2025-12-29 12:20 UTC  =?UTF-8?b?0J3QuNC60L7Qu9Cw0Lkg0KTQsNC00LXQtdCy?= <fadeymail@rambler.ru>
` Re: BUG #19367: typos in backend/utils/adt/timestamp.c
  2025-12-29 15:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19367: typos in backend/utils/adt/timestamp.c
  2025-12-30 02:30 UTC  Japin Li <japinli@hotmail.com>
  [6+ 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