pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17738: There is a typo on your website
2023-01-06 18:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17738: There is a typo on your website
2023-01-07 13:56 UTC Magnus Hagander <magnus@hagander.net>
[2+ messages in thread]
Segfault while creating logical replication slots on active DB 14.6-1 + 15.1-1
2022-12-14 22:59 UTC Alex Richman <alexrichman@onesignal.com>
` Re: Segfault while creating logical replication slots on active DB 14.6-1 + 15.1-1
2022-12-15 03:06 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Segfault while creating logical replication slots on active DB 14.6-1 + 15.1-1
2023-01-03 12:56 UTC Alex Richman <alexrichman@onesignal.com>
` Re: Segfault while creating logical replication slots on active DB 14.6-1 + 15.1-1
2023-01-06 07:11 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Segfault while creating logical replication slots on active DB 14.6-1 + 15.1-1
2023-01-06 15:19 UTC Alex Richman <alexrichman@onesignal.com>
` Re: Segfault while creating logical replication slots on active DB 14.6-1 + 15.1-1
2023-01-07 07:35 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[6+ messages in thread]
BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-13 10:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-15 18:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-15 20:06 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-15 21:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-16 04:39 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-16 14:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-16 18:47 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-16 20:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-18 02:21 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-18 02:23 UTC Christophe Pettus <xof@thebuild.com>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-18 23:55 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-19 03:21 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-28 20:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-28 21:12 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-28 21:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-28 21:21 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-28 21:23 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-28 22:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-29 01:23 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-29 01:29 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-29 02:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-29 03:03 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-29 17:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-29 18:26 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-29 18:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-29 18:52 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-29 20:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2022-12-29 21:37 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)
2023-01-06 17:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[29+ messages in thread]
Issue with SQL query causing unintended consequences in database
2023-01-06 12:56 UTC prevot morvan <prevotmorvan@yahoo.fr>
` Re: Issue with SQL query causing unintended consequences in database
2023-01-06 14:37 UTC Pantelis Theodosiou <ypercube@gmail.com>
[2+ messages in thread]
BUG #17737: An assert failed in execExprInterp.c
2023-01-05 16:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17737: An assert failed in execExprInterp.c
2023-01-05 20:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17737: An assert failed in execExprInterp.c
2023-01-05 21:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17737: An assert failed in execExprInterp.c
2023-01-05 21:41 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17737: An assert failed in execExprInterp.c
2023-01-06 00:01 UTC Andres Freund <andres@anarazel.de>
[5+ messages in thread]
BUG #17736: when psql -c is used, the $ sign is escaped
2023-01-04 02:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17736: when psql -c is used, the $ sign is escaped
2023-01-04 13:34 UTC John Naylor <john.naylor@enterprisedb.com>
[2+ messages in thread]
BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG
2022-12-13 07:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG
2022-12-13 11:03 UTC Bowen Shi <zxwsbg12138@gmail.com>
` Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG
2022-12-19 11:27 UTC shveta malik <shveta.malik@gmail.com>
` Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG
2022-12-19 12:22 UTC Bowen Shi <zxwsbg12138@gmail.com>
` Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG
2022-12-20 06:10 UTC shveta malik <shveta.malik@gmail.com>
` Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG
2022-12-20 12:02 UTC shveta malik <shveta.malik@gmail.com>
` Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG
2022-12-21 05:15 UTC Bowen Shi <zxwsbg12138@gmail.com>
` Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG
2022-12-21 09:06 UTC shveta malik <shveta.malik@gmail.com>
` Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG
2023-01-03 03:55 UTC Amit Kapila <amit.kapila16@gmail.com>
[9+ messages in thread]
BUG #17735: Uninstall of one version wipes out logs for all versions
2023-01-02 20:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17735: Uninstall of one version wipes out logs for all versions
2023-01-03 00:03 UTC Sam Bortman <sam.bortman@gmail.com>
[2+ messages in thread]
PostgreSQL 15 on Fedora 37 Does not start after reboot
2023-01-01 22:55 UTC Tom Dryden <tdryden@comcast.net>
` Re: PostgreSQL 15 on Fedora 37 Does not start after reboot
2023-01-01 23:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 15 on Fedora 37 Does not start after reboot
2023-01-02 17:47 UTC Tom Dryden <tdryden@comcast.net>
` Re: PostgreSQL 15 on Fedora 37 Does not start after reboot
2023-01-02 17:56 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: PostgreSQL 15 on Fedora 37 Does not start after reboot
2023-01-02 18:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #17734: Doc bug: "initial database user" used where "bootstrap superuser" is meant
2022-12-29 18:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17734: Doc bug: "initial database user" used where "bootstrap superuser" is meant
2022-12-29 20:35 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17734: Doc bug: "initial database user" used where "bootstrap superuser" is meant
2022-12-29 21:30 UTC Bryn Llewellyn <bryn@yugabyte.com>
[3+ messages in thread]
postgres reorders expressions when inlining
2022-12-29 10:58 UTC Floris Van Nee <florisvannee@Optiver.com>
` Re: postgres reorders expressions when inlining
2022-12-29 14:02 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: postgres reorders expressions when inlining
2022-12-29 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17732: pg_restore fails with check constraint
2022-12-27 10:14 UTC PG Bug reporting form <noreply@postgresql.org>
` BUG #17732: pg_restore fails with check constraint
2022-12-28 17:08 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
[PATCH v1 3/3] update datfrozenxid/datminmxid once per database in vacuumdb
2022-12-28 00:59 UTC Nathan Bossart <nathandbossart@gmail.com>
[PATCH v1 2/3] introduce pg_update_datfrozenxid
2022-12-28 00:20 UTC Nathan Bossart <nathandbossart@gmail.com>
[PATCH v1 1/3] add UPDATE_DATFROZENXID option to VACUUM
2022-12-27 23:21 UTC Nathan Bossart <nathandbossart@gmail.com>
BUG #17730: Trigger Issue
2022-12-23 17:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17730: Trigger Issue
2022-12-23 18:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17730: Trigger Issue
2022-12-23 18:45 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
[PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE
2022-08-03 06:37 UTC 王海洋 <wanghaiyang.001@bytedance.com>
` Re: [PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE
2022-08-04 07:55 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: [PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE
2022-08-04 08:12 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: [External] Re: [PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE
2022-08-04 10:26 UTC 王海洋 <wanghaiyang.001@bytedance.com>
` Re: [External] Re: [PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE
2022-08-05 13:17 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: [External] Re: [PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE
2022-08-05 14:01 UTC 王海洋 <wanghaiyang.001@bytedance.com>
` Re: [External] Re: [PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE
2022-08-05 16:05 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` [PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE
2022-12-23 13:54 UTC Karina Litskevich <litskevichkarina@gmail.com>
` Re: [PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE
2022-12-23 16:35 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: [PATCH] BUG FIX: inconsistent page found in BRIN_REGULAR_PAGE
2022-12-23 17:50 UTC Patrick Headley <pheadley@linxco-inc.com>
[10+ messages in thread]
BUG #17728: When jdbc calls the stored procedure, portal->stmts in FillPortalStore is null, causing a processing
2022-12-22 12:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17728: When jdbc calls the stored procedure, portal->stmts in FillPortalStore is null, causing a processing
2022-12-22 19:25 UTC Dave Cramer <davecramer@postgres.rocks>
` Re: BUG #17728: When jdbc calls the stored procedure, portal->stmts in FillPortalStore is null, causing a processing
2022-12-23 04:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17727: A query crashes server process: ... was terminated by signal 7: Bus error / Segmentation Fault
2022-12-21 19:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17727: A query crashes server process: ... was terminated by signal 7: Bus error / Segmentation Fault
2022-12-21 19:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17725: Sefault when seg_in() called with a large argument
2022-12-20 03:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17725: Sefault when seg_in() called with a large argument
2022-12-20 10:13 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: BUG #17725: Sefault when seg_in() called with a large argument
2022-12-20 12:48 UTC Robins Tharakan <tharakan@gmail.com>
` Re: BUG #17725: Sefault when seg_in() called with a large argument
2022-12-20 16:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17725: Sefault when seg_in() called with a large argument
2022-12-20 17:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #17713: Assert with postgres_fdw in v12
2022-12-12 04:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17713: Assert with postgres_fdw in v12
2022-12-13 03:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17713: Assert with postgres_fdw in v12
2022-12-14 10:02 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17713: Assert with postgres_fdw in v12
2022-12-15 12:33 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17713: Assert with postgres_fdw in v12
2022-12-19 12:03 UTC Robins Tharakan <tharakan@gmail.com>
[5+ messages in thread]
BUG #17724: All autovacuum workers operate on 1 db at a time
2022-12-16 17:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17724: All autovacuum workers operate on 1 db at a time
2022-12-16 21:26 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #17723: cache lookup failed for type 0
2022-12-16 15:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17723: cache lookup failed for type 0
2022-12-16 17:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17723: cache lookup failed for type 0
2022-12-16 19:36 UTC Vik Fearing <vik@postgresfriends.org>
[3+ messages in thread]
pg_rewind succeed but postgresql showing error when trying to make standby with common ancestor
2022-12-15 09:33 UTC niraj nandane <niraj.nandane@gmail.com>
` Re: pg_rewind succeed but postgresql showing error when trying to make standby with common ancestor
2022-12-16 02:11 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: pg_rewind succeed but postgresql showing error when trying to make standby with common ancestor
2022-12-16 06:03 UTC niraj nandane <niraj.nandane@gmail.com>
[3+ messages in thread]
BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-09 15:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-10 02:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-12 14:37 UTC Jean-Francois Levesque <jf.levesque@gmail.com>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-12 18:36 UTC Jean-Francois Levesque <jf.levesque@gmail.com>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-13 01:40 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-13 01:46 UTC Jean-Francois Levesque <jf.levesque@gmail.com>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-13 02:39 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-15 20:41 UTC Jean-Francois Levesque <jf.levesque@gmail.com>
[8+ 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