pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedToasted column values during replication. (Enhancement)
2023-06-30 17:10 UTC Chandy G <vgchandru@yahoo.com>
` Re: Toasted column values during replication. (Enhancement)
2023-07-03 08:50 UTC Amit Kapila <amit.kapila16@gmail.com>
[2+ messages in thread]
BUG #18000: Access method used by matview can be dropped leaving broken matview
2023-06-26 08:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
2023-06-26 08:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
2023-06-27 04:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
2023-06-27 06:33 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
2023-06-27 17:03 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
2023-06-27 18:23 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
2023-06-27 23:11 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
2023-06-27 23:19 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
2023-06-28 22:57 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
2023-07-03 02:26 UTC Michael Paquier <michael@paquier.xyz>
[10+ messages in thread]
BUG #5276: pg_ctl reads data directory on -D instead of postgresql.conf directoryh
2010-01-14 02:01 UTC James Bellinger <jfb@zer7.com>
` Re: BUG #5276: pg_ctl reads data directory on -D instead of postgresql.conf directoryh
2010-01-14 16:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` BUG #18002: Duplicate entries of row possible even after having primary key
2023-06-27 11:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18002: Duplicate entries of row possible even after having primary key
2023-06-27 20:36 UTC Andres Freund <andres@anarazel.de>
` RE: BUG #18002: Duplicate entries of row possible even after having primary key
2023-06-28 08:38 UTC Ajinkya Tankhiwale <ajinkya.tankhiwale@tcs.com>
` Re: BUG #18002: Duplicate entries of row possible even after having primary key
2023-06-28 10:28 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18002: Duplicate entries of row possible even after having primary key
2023-06-28 20:59 UTC Andres Freund <andres@anarazel.de>
` RE: BUG #18002: Duplicate entries of row possible even after having primary key
2023-06-29 12:12 UTC Ajinkya Tankhiwale <ajinkya.tankhiwale@tcs.com>
` Re: BUG #18002: Duplicate entries of row possible even after having primary key
2023-07-02 21:53 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18002: Duplicate entries of row possible even after having primary key
2023-07-03 01:06 UTC Peter Geoghegan <pg@bowt.ie>
[10+ messages in thread]
BUG #18011: Declarative partition privilege problem cause incorrect execution plans
2023-07-01 07:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18011: Declarative partition privilege problem cause incorrect execution plans
2023-07-01 21:11 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
BUG #5273: Unexpected function behavior/failure
2010-01-12 22:30 UTC Vee <sefer@hotmail.com>
` Re: BUG #5273: Unexpected function behavior/failure
2010-01-13 00:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #5273: Unexpected function behavior/failure
2010-01-13 01:48 UTC Robert Haas <robertmhaas@gmail.com>
` BUG #18005: PSQL Process hangs in parallel mode
2023-06-29 06:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18005: PSQL Process hangs in parallel mode
2023-06-29 11:46 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` BUG #18005: PSQL Process hangs in parallel mode / complement information
2023-06-30 13:19 UTC ess.bee59@gmail.com
` BUG #18005: PSQL Process hangs in parallel mode / complement information
2023-07-01 14:37 UTC ess.bee59@gmail.com
[7+ messages in thread]
BUG #18010: Bug with installation/auto-configuration
2023-07-01 04:45 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #5272: PL/Python SELECT: return composite fields as dict, not str
2010-01-11 16:41 UTC Steve White <swhite@aip.de>
` Re: BUG #5272: PL/Python SELECT: return composite fields as dict, not str
2010-01-12 02:31 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #5272: PL/Python SELECT: return composite fields as dict, not str
2010-01-31 12:20 UTC Steve White <swhite@aip.de>
` Re: “server closed the connection unexpectedly”
2014-06-18 18:45 UTC Heikki Linnakangas <hlinnakangas@vmware.com>
` Re: “server closed the connection unexpectedly”
2014-06-18 18:51 UTC Felipe Gasper <felipe@felipegasper.com>
` Re: “server closed the connection unexpectedly”
2014-06-18 20:09 UTC Felipe Gasper <felipe@felipegasper.com>
` server closed the connection unexpectedly during upgrade
2015-12-16 07:34 UTC Yang, Leo <leo.yang@hp.com>
` Re: server closed the connection unexpectedly during upgrade
2015-12-16 07:57 UTC Michael Paquier <michael.paquier@gmail.com>
` Re: server closed the connection unexpectedly during upgrade
2015-12-16 08:26 UTC Yang, Leo <leo.yang@hp.com>
` server closed the connection unexpectedly - bug report
2022-06-25 16:00 UTC Jiří Ledvinka <ledvinkaj@sci.muni.cz>
` Re: server closed the connection unexpectedly - bug report
2022-06-25 21:11 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: server closed the connection unexpectedly - bug report
2022-06-25 21:22 UTC David G. Johnston <david.g.johnston@gmail.com>
` RE: server closed the connection unexpectedly - bug report
2022-07-11 08:05 UTC Jiří Ledvinka <ledvinkaj@sci.muni.cz>
` Server closed the connection unexpectedly
2023-06-15 16:26 UTC Zu-Ming Jiang <zuming.jiang@inf.ethz.ch>
` Re: Server closed the connection unexpectedly
2023-06-15 20:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Server closed the connection unexpectedly (memory leak)
2023-06-23 16:06 UTC Zu-Ming Jiang <zuming.jiang@inf.ethz.ch>
` Fwd: Server closed the connection unexpectedly (memory leak)
2023-06-23 16:20 UTC Zu-Ming Jiang <zuming.jiang@inf.ethz.ch>
` Re: Server closed the connection unexpectedly (memory leak)
2023-06-24 16:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Server closed the connection unexpectedly (memory leak)
2023-07-01 02:56 UTC Andres Freund <andres@anarazel.de>
[19+ messages in thread]
BUG #18006: recovery_target_action=shutdown triggers automatic recovery on next startup (beyond point in time)
2023-06-29 08:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18006: recovery_target_action=shutdown triggers automatic recovery on next startup (beyond point in time)
2023-06-30 02:50 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[2+ messages in thread]
BUG #18007: age(timestamp, timestamp) is marked as immutable, but using age(date, date) says it's not
2023-06-29 17:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18007: age(timestamp, timestamp) is marked as immutable, but using age(date, date) says it's not
2023-06-29 17:45 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18007: age(timestamp, timestamp) is marked as immutable, but using age(date, date) says it's not
2023-06-29 17:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18007: age(timestamp, timestamp) is marked as immutable, but using age(date, date) says it's not
2023-06-29 18:20 UTC Braiam <braiamp@gmail.com>
` Re: BUG #18007: age(timestamp, timestamp) is marked as immutable, but using age(date, date) says it's not
2023-06-29 18:23 UTC Braiam <braiamp@gmail.com>
` Re: BUG #18007: age(timestamp, timestamp) is marked as immutable, but using age(date, date) says it's not
2023-06-29 18:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18007: age(timestamp, timestamp) is marked as immutable, but using age(date, date) says it's not
2023-06-29 18:29 UTC Braiam <braiamp@gmail.com>
` Re: BUG #18007: age(timestamp, timestamp) is marked as immutable, but using age(date, date) says it's not
2023-06-29 19:25 UTC Christophe Pettus <xof@thebuild.com>
` Re: BUG #18007: age(timestamp, timestamp) is marked as immutable, but using age(date, date) says it's not
2023-06-29 19:58 UTC Braiam <braiamp@gmail.com>
[9+ messages in thread]
BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-27 20:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-27 21:06 UTC Joe Conway <mail@joeconway.com>
` Re: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-27 21:24 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-27 21:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-28 00:03 UTC Andres Freund <andres@anarazel.de>
[5+ messages in thread]
No -d option
2023-06-16 05:35 UTC bowen zhao <zwcbowen@gmail.com>
` Re: No -d option
2023-06-16 08:13 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: No -d option
2023-06-27 05:52 UTC bowen zhao <zwcbowen@gmail.com>
[3+ messages in thread]
BUG #18001: Invalid subquery passed as true
2023-06-26 10:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18001: Invalid subquery passed as true
2023-06-26 11:34 UTC Julien Rouhaud <rjuju123@gmail.com>
[2+ messages in thread]
BUG #17998: Postgres crashes when executing WorkTableScan.
2023-06-26 03:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17998: Postgres crashes when executing WorkTableScan.
2023-06-26 08:43 UTC Heikki Linnakangas <hlinnaka@iki.fi>
[2+ messages in thread]
BUG #17999: comment to BUG 17990 (PSQL Process hangs in parallel mode)
2023-06-26 07:06 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-24 18:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-24 19:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-24 20:48 UTC Willian Colognesi <willian_colognesi@trimble.com>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-25 03:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-26 04:21 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-26 04:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-26 04:56 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-26 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
[8+ messages in thread]
BUG #17993: FK issue on logical replication table
2023-06-24 06:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17993: FK issue on logical replication table
2023-06-26 04:42 UTC Amit Kapila <amit.kapila16@gmail.com>
[2+ messages in thread]
回复: BUG #17998: Postgres crashes when executing WorkTableScan.
2023-06-26 03:53 UTC 梁 成林 <chenglin-liang@outlook.com>
BUG #17990: PSQL Process hangs in parallel mode
2023-06-22 20:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17990: PSQL Process hangs in parallel mode
2023-06-25 22:12 UTC Thomas Munro <thomas.munro@gmail.com>
[2+ messages in thread]
range canonicalization function make corner case failed.
2023-06-25 03:12 UTC jian he <jian.universality@gmail.com>
BUG #17991: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-22 23:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17991: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-23 09:37 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #17991: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-23 11:09 UTC Julien Rouhaud <rjuju123@gmail.com>
[3+ messages in thread]
BUG #17992: Followed instructions to setup Postgresql but systemctl restart postgresql-15.service
2023-06-23 08:27 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17989: ERROR: could not open file "pg_logical/snapshots/6-1E182808.snap": Permission denied
2023-06-22 10:26 UTC PG Bug reporting form <noreply@postgresql.org>
Small subset of man pages available after install from Redhat-compatible repo
2023-06-21 21:16 UTC Linus Hicks <linus.hicks@highstreetit.com>
` Re: Small subset of man pages available after install from Redhat-compatible repo
2023-06-22 06:39 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #17988: psql generates segfault when connecting to remote database
2023-06-21 17:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17988: psql generates segfault when connecting to remote database
2023-06-21 20:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17987: zypper refresh failed when installed the postgresql
2023-06-21 09:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17987: zypper refresh failed when installed the postgresql
2023-06-21 11:17 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re:Re: BUG #17987: zypper refresh failed when installed the postgresql
2023-06-21 14:14 UTC 270246512 <270246512@qq.com>
` Re: Re: BUG #17987: zypper refresh failed when installed the postgresql
2023-06-21 16:08 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[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