pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17822: Some scripts are blocked by Device Guard
2023-03-05 04:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17822: Some scripts are blocked by Device Guard
2023-03-05 23:18 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-01 19:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-01 20:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 11:21 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 14:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 15:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 18:17 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 18:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 19:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
[8+ messages in thread]
BUG #17819: The assert failed #17334 has not been repaired
2023-03-02 11:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17819: The assert failed #17334 has not been repaired
2023-03-02 16:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17818: CTE is not returning the right data.
2023-03-02 08:33 UTC PG Bug reporting form <noreply@postgresql.org>
` BUG #17818: CTE is not returning the right data.
2023-03-02 13:28 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17818: CTE is not returning the right data.
2023-03-02 15:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-01 05:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-01 09:31 UTC Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-01 11:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-02 05:05 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-02 06:14 UTC Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-02 07:02 UTC Michael Paquier <michael@paquier.xyz>
[6+ messages in thread]
BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-02-28 03:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-02-28 13:52 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 02:01 UTC Keyerror Smart <smartkeyerror@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 02:52 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 03:02 UTC Keyerror Smart <smartkeyerror@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 03:40 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 04:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 04:55 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 06:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 07:15 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 13:22 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 15:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 16:35 UTC David G. Johnston <david.g.johnston@gmail.com>
[13+ messages in thread]
BUG #17816: Invalid memory access in translate function
2023-03-01 08:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17816: Invalid memory access in translate function
2023-03-01 15:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Gpg error with Postgresql aarch64 repo - PG14
2023-03-01 12:40 UTC Felipe Die <felipedie@gmail.com>
Memory leakage in libpq valgrind test
2023-03-01 06:34 UTC Sudheer H R <sudheer.hr@tekenlight.com>
` Re: Memory leakage in libpq valgrind test
2023-03-01 06:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Memory leakage in libpq valgrind test
2023-03-01 06:59 UTC Michael Paquier <michael@paquier.xyz>
` Re: Memory leakage in libpq valgrind test
2023-03-01 07:05 UTC Sudheer H R <sudheer.hr@tekenlight.com>
[4+ messages in thread]
Crash during backend start when low on memory
2022-12-14 12:58 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2022-12-14 13:23 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Crash during backend start when low on memory
2022-12-14 15:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Crash during backend start when low on memory
2022-12-14 21:14 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2022-12-14 21:21 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2022-12-15 17:20 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Crash during backend start when low on memory
2022-12-16 08:46 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-01-13 10:05 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-01-13 11:53 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Crash during backend start when low on memory
2023-01-13 15:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Crash during backend start when low on memory
2023-01-16 10:09 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-01-16 20:52 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-01-16 20:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Crash during backend start when low on memory
2023-01-16 21:10 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-01-16 21:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Crash during backend start when low on memory
2023-02-05 21:00 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-02-05 23:18 UTC Andres Freund <andres@anarazel.de>
` Re: Crash during backend start when low on memory
2023-02-06 07:37 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-02-06 15:50 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-02-06 18:41 UTC Andres Freund <andres@anarazel.de>
` Re: Crash during backend start when low on memory
2023-02-28 20:39 UTC Mats Kindahl <mats@timescale.com>
[21+ messages in thread]
BUG #17814: Detail info on kerbos authentication
2023-02-28 18:44 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 15:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 16:28 UTC Cherio <cherio@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 16:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 17:31 UTC Cherio <cherio@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 17:54 UTC Cherio <cherio@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 18:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 18:06 UTC Cherio <cherio@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 18:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 18:41 UTC Cherio <cherio@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 19:29 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 19:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 20:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 20:36 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-28 14:53 UTC Cherio <cherio@gmail.com>
[14+ messages in thread]
BUG #17813: I have an error about the installation of PostgreSQL installer on every version. please help.
2023-02-28 04:04 UTC PG Bug reporting form <noreply@postgresql.org>
Regarding backpatching to v14
2023-02-27 10:32 UTC niraj nandane <niraj.nandane@gmail.com>
` Re: Regarding backpatching to v14
2023-02-27 23:40 UTC Michael Paquier <michael@paquier.xyz>
[2+ messages in thread]
BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-01-10 07:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-01-13 09:36 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-01 02:47 UTC Bowen Shi <zxwsbg12138@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-01 15:32 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-02 07:45 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-21 03:51 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-21 06:22 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-21 07:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-22 10:27 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-24 00:36 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-24 11:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-24 19:56 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-25 03:39 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-25 20:38 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-27 00:08 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-27 03:01 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-27 04:01 UTC Michael Paquier <michael@paquier.xyz>
[17+ messages in thread]
BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-18 08:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-20 22:49 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 04:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 05:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 17:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 19:33 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 20:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 20:17 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 20:42 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 20:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 22:16 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 22:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 23:33 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-22 00:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-22 01:17 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-22 19:23 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-22 21:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-23 18:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-23 21:00 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-23 22:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-23 23:36 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 01:54 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 17:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 17:44 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 17:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 22:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 22:53 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 23:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 23:57 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-25 19:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-25 20:19 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-25 20:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-25 21:46 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-25 21:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
[34+ messages in thread]
BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-21 09:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-21 11:56 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-21 15:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-21 17:15 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-21 18:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-22 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-22 09:07 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-22 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-22 12:29 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-23 11:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-23 12:00 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-23 21:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-23 23:20 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-24 08:50 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-24 16:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-25 15:08 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-25 16:00 UTC Alexander Lakhin <exclusion@gmail.com>
[17+ messages in thread]
two bugs
2023-02-25 01:43 UTC zhxpgh <zhxpgh@foxmail.com>
` Re: two bugs
2023-02-25 13:37 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
[2+ messages in thread]
BUG #17806: PostgreSQL 13.10 returns "CREATE DATABASE cannot be executed within a pipeline"
2023-02-23 22:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17806: PostgreSQL 13.10 returns "CREATE DATABASE cannot be executed within a pipeline"
2023-02-24 15:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17806: PostgreSQL 13.10 returns "CREATE DATABASE cannot be executed within a pipeline"
2023-02-24 19:36 UTC Wesley Smith <wesley.smith@exterro.com>
[3+ messages in thread]
pg_upgrade does not support a table 2 in the original database to inherit from table 1 (field F_Test1 is not empty), and then table 2 modifies F by itself_ Test1 is nullable
2023-02-24 03:22 UTC 小杨 <17097859508@qq.com>
[PATCH v2] WIP: generate explicit expression step to evaluate correlated MULTIEXPR_SUBLINK
2023-02-24 01:48 UTC Andres Freund <andres@anarazel.de>
[BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-02-08 14:48 UTC Mead, Scott <meads@amazon.com>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-02-12 20:03 UTC David Zhang <david.zhang@highgo.ca>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-03-02 01:43 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-04-14 14:17 UTC Mead, Scott <meads@amazon.com>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-05-26 08:00 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-10-26 15:23 UTC Scott Mead <scott@meads.us>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-11-19 18:36 UTC Scott Mead <scott@meads.us>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-11-22 04:36 UTC Jobin Augustine <jobin.augustine@percona.com>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2023-01-23 17:23 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2023-01-31 15:35 UTC Scott Mead <scott@meads.us>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2023-02-23 22:22 UTC Melanie Plageman <melanieplageman@gmail.com>
[11+ messages in thread]
BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 09:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 12:54 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 13:02 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 15:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 15:51 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 15:59 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 16:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 16:34 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 22:30 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 23:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 13:18 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 15:30 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 15:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 16:08 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 16:12 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 17:02 UTC reiner peterke <zedaardv@gmail.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-16 08:07 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-16 16:03 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-16 16:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-16 18:14 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-16 18:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2023-02-23 21:07 UTC Daniel Gustafsson <daniel@yesql.se>
[22+ messages in thread]
[PATCH v1] heavily-WIP: partition specific subplan plans
2023-02-22 19:03 UTC Andres Freund <andres@anarazel.de>
Re: pg_dump error
2003-07-29 15:59 UTC Vasko Miovski <vasko.miovski@cybertechne.com>
` pg_dump Error
2004-01-30 13:40 UTC yogesh sailukar <sailukar_yogesh@yahoo.com>
` pg_dump: error
2023-02-22 16:17 UTC Alessandro Papa - Infolab <a.papa@infolabonline.com>
` Re: pg_dump: error
2023-02-22 16:44 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: pg_dump: error
2023-02-22 17:15 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[5+ 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