pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18559: Crash after detaching a partition concurrently from another session
2024-07-30 13:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-07-30 13:52 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-07-31 02:34 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-10 13:54 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-12 18:24 UTC Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-12 22:33 UTC Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-13 12:12 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-13 18:18 UTC Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-15 19:31 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-18 14:46 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-20 18:46 UTC Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-22 15:14 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
[12+ messages in thread]
BUG #18507: See C include file "ntstatus.h" for a description of the hexadecimal value.
2024-06-13 07:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18507: See C include file "ntstatus.h" for a description of the hexadecimal value.
2024-08-21 17:21 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[2+ messages in thread]
REINDEX INDEX pg_catalog.pg_default_acl_role_nsp_obj_index stuck waiting for transaction from the future in PG 13.16
2024-08-16 08:29 UTC Marcin Barczyński <mba.ogolny@gmail.com>
` Re: REINDEX INDEX pg_catalog.pg_default_acl_role_nsp_obj_index stuck waiting for transaction from the future in PG 13.16
2024-08-16 17:54 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: REINDEX INDEX pg_catalog.pg_default_acl_role_nsp_obj_index stuck waiting for transaction from the future in PG 13.16
2024-08-21 14:49 UTC Marcin Barczyński <mba.ogolny@gmail.com>
[3+ messages in thread]
CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-20 09:00 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-20 14:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-20 17:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-21 06:14 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-21 07:55 UTC Richard Guo <guofenglinux@gmail.com>
` Re: CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-21 14:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column)
2024-08-21 12:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column)
2024-08-21 13:17 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column)
2024-08-21 13:30 UTC Rémi Cura <remi.cura@gmail.com>
[3+ messages in thread]
BUG #18586: Process (and transaction) is stuck in IPC when the DB is under high load
2024-08-21 11:53 UTC PG Bug reporting form <noreply@postgresql.org>
server crash on raspberry pi for large queries
2024-08-20 00:45 UTC Matthew Clark <mclark@drmatthewclark.com>
` Re: server crash on raspberry pi for large queries
2024-08-20 13:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: server crash on raspberry pi for large queries
2024-08-20 19:18 UTC Matthew Clark <mclark@drmatthewclark.com>
` Re: server crash on raspberry pi for large queries
2024-08-21 02:38 UTC David Rowley <dgrowleyml@gmail.com>
[4+ messages in thread]
FDW INSERT batching can change behavior
2024-08-09 03:07 UTC git@jasonk.me
` Re: FDW INSERT batching can change behavior
2024-08-09 19:55 UTC Tomas Vondra <tomas@vondra.me>
` Re: FDW INSERT batching can change behavior
2024-08-13 04:57 UTC Jason Kim <git@jasonk.me>
` Re: FDW INSERT batching can change behavior
2024-08-13 12:12 UTC Tomas Vondra <tomas@vondra.me>
` Re: FDW INSERT batching can change behavior
2024-08-13 18:31 UTC Tomas Vondra <tomas@vondra.me>
` Re: FDW INSERT batching can change behavior
2024-08-14 11:31 UTC Tomas Vondra <tomas@vondra.me>
` Re: FDW INSERT batching can change behavior
2024-08-20 21:47 UTC Tomas Vondra <tomas@vondra.me>
[7+ messages in thread]
BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-07 15:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-08 10:44 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-08 17:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-08 20:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-09 03:25 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-09 03:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-09 15:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-19 11:23 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-19 16:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-19 17:11 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-19 17:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-19 19:16 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-20 09:43 UTC Andrei Lepikhov <lepihov@gmail.com>
[13+ messages in thread]
Report Postgres Bug - Unlogged table sequence
2024-08-19 05:47 UTC Sindhu S <sindhusanti@gmail.com>
` Re: Report Postgres Bug - Unlogged table sequence
2024-08-19 08:57 UTC Aleksander Alekseev <aleksander@timescale.com>
` Re: Report Postgres Bug - Unlogged table sequence
2024-08-19 13:41 UTC Zaid Shabbir <zaidshabbir@gmail.com>
` Re: Report Postgres Bug - Unlogged table sequence
2024-08-20 03:37 UTC Sindhu S <sindhusanti@gmail.com>
[4+ messages in thread]
Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-22 14:46 UTC Mohammed Siddiqui <msiddiqui@net32.com>
` Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-23 08:33 UTC Aleksander Alekseev <aleksander@timescale.com>
` RE: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-25 03:51 UTC Mohammed Siddiqui <msiddiqui@net32.com>
` Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-30 12:36 UTC Muhammad Waqas <waqas.m@bitnine.net>
` Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-30 13:15 UTC Zaid Shabbir <zaidshabbir@gmail.com>
` RE: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-30 13:34 UTC Mohammed Siddiqui <msiddiqui@net32.com>
` Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-30 13:41 UTC Zaid Shabbir <zaidshabbir@gmail.com>
` Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-08-19 17:20 UTC Bruce Momjian <bruce@momjian.us>
[8+ messages in thread]
TLS session tickets disabled?
2024-08-12 21:19 UTC Cameron Vogt <cvogt@automaticcontrols.net>
` Re: TLS session tickets disabled?
2024-08-13 18:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: TLS session tickets disabled?
2024-08-13 20:59 UTC Cameron Vogt <cvogt@automaticcontrols.net>
` Re: TLS session tickets disabled?
2024-08-14 21:59 UTC Cameron Vogt <cvogt@automaticcontrols.net>
` Re: TLS session tickets disabled?
2024-08-15 17:52 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: TLS session tickets disabled?
2024-08-15 19:33 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: TLS session tickets disabled?
2024-08-16 07:49 UTC Fire Emerald <fire.github@gmail.com>
` Re: TLS session tickets disabled?
2024-08-16 08:11 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: TLS session tickets disabled?
2024-08-16 14:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: TLS session tickets disabled?
2024-08-16 19:11 UTC Cameron Vogt <cvogt@automaticcontrols.net>
` Re: TLS session tickets disabled?
2024-08-16 23:00 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: TLS session tickets disabled?
2024-08-17 21:27 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: TLS session tickets disabled?
2024-08-19 12:52 UTC Daniel Gustafsson <daniel@yesql.se>
[13+ messages in thread]
BUG #18582: fixed range of search for empty slot in SLRU
2024-08-13 12:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18582: fixed range of search for empty slot in SLRU
2024-08-13 18:32 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18582: fixed range of search for empty slot in SLRU
2024-08-19 01:20 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18582: fixed range of search for empty slot in SLRU
2024-08-19 09:40 UTC Sergey Sargsyan <sergey.sargsyan.2001@gmail.com>
[4+ messages in thread]
BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command
2024-02-07 02:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command
2024-02-07 04:01 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command
2024-02-07 07:49 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command
2024-02-07 19:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command
2024-08-17 05:21 UTC Imran Zaheer <imran.zhir@gmail.com>
` Re: BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command
2024-08-17 18:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command
2024-08-17 19:36 UTC Bruce Momjian <bruce@momjian.us>
[7+ messages in thread]
BUG #18584: Triggers are not fired or executing when any DML transaction runs
2024-08-17 09:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18584: Triggers are not fired or executing when any DML transaction runs
2024-08-17 16:37 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18583: jsonb_populate_record return values cannot be queried correctly in subselects
2024-08-14 14:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18583: jsonb_populate_record return values cannot be queried correctly in subselects
2024-08-15 18:30 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18583: jsonb_populate_record return values cannot be queried correctly in subselects
2024-08-16 19:52 UTC Robert Greig <robert.j.greig@gmail.com>
[3+ messages in thread]
BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-16 12:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-16 12:21 UTC Michael Bondarenko <work.michael.2956@gmail.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-16 12:44 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-16 13:02 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-17 01:47 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-17 08:00 UTC Michael Bondarenko <work.michael.2956@gmail.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-17 15:12 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-17 18:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-17 20:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-18 01:48 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-18 02:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-19 17:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-20 03:56 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-20 19:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-20 20:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-02-29 10:30 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-05-07 21:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-05-07 22:09 UTC Wetmore, Matthew (CTR) <Matthew.Wetmore@evernorth.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-05-08 01:03 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-05-08 13:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-05-08 14:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-05-18 14:02 UTC Martijn Wallet <martijn@dbre.nu>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-05-18 14:47 UTC Martijn Wallet <martijn@dbre.nu>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-07-08 17:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-07-12 16:35 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-08-16 02:45 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-08-16 15:26 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-08-16 15:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-08-16 15:52 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-08-16 16:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
2024-08-16 16:15 UTC Bruce Momjian <bruce@momjian.us>
[31+ messages in thread]
Using current_user as an argument of pl/pgsql function affects collation of other arguments
2024-08-14 14:09 UTC Dmytro Astapov <dastapov@gmail.com>
` Re: Using current_user as an argument of pl/pgsql function affects collation of other arguments
2024-08-15 20:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18580: The pg_similarity appears to be wrong
2024-08-12 09:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18580: The pg_similarity appears to be wrong
2024-08-15 15:13 UTC Euler Taveira <euler@eulerto.com>
[2+ messages in thread]
BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-07-27 09:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-07-29 01:53 UTC Peter Smith <smithpb2250@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-07-29 02:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-07-29 02:45 UTC Peter Smith <smithpb2250@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-07-29 03:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-07-29 05:18 UTC Peter Smith <smithpb2250@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-07-29 06:14 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-07-29 08:10 UTC Peter Smith <smithpb2250@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-07-29 14:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-07-29 14:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-02 02:51 UTC Peter Smith <smithpb2250@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-02 14:14 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-05 07:43 UTC Peter Smith <smithpb2250@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-12 07:44 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-14 04:51 UTC Peter Smith <smithpb2250@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-14 22:28 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-14 22:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-14 22:46 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-14 22:54 UTC Peter Smith <smithpb2250@gmail.com>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-14 23:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column
2024-08-15 01:12 UTC David Rowley <dgrowleyml@gmail.com>
[21+ messages in thread]
Certain options in pg_upgrade don't seem to work.
2024-08-14 01:41 UTC DBA <ecountdba@ecounterp.co.kr>
` Re: Certain options in pg_upgrade don't seem to work.
2024-08-14 17:54 UTC Tomas Vondra <tomas@vondra.me>
[2+ messages in thread]
BUG #18581: psql symbol append_history not found when quitting
2024-08-13 09:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18581: psql symbol append_history not found when quitting
2024-08-13 18:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18581: psql symbol append_history not found when quitting
2024-08-14 05:45 UTC Rainer J.H. Brandt <rjhb@bb-c.de>
[3+ messages in thread]
a row is not inserted in nested INSERT ON CONFLICT
2024-08-13 04:17 UTC Jason Kim <git@jasonk.me>
` Re: a row is not inserted in nested INSERT ON CONFLICT
2024-08-13 19:23 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-05 09:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-05 12:51 UTC Bernd Helmle <mailings@oopsware.de>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-05 15:49 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-05 22:14 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-05 22:32 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-06 13:11 UTC Christoph Berg <myon@debian.org>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-11 07:18 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-11 08:15 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-12 03:31 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-16 02:01 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-16 08:13 UTC Christoph Berg <myon@debian.org>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-17 23:10 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-17 23:51 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-18 09:30 UTC Christoph Berg <myon@debian.org>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-18 20:25 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-18 20:57 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«
2019-07-18 21:27 UTC Peter Geoghegan <pg@bowt.ie>
` [PATCH] Search for SLRU page only in its own bank
2024-08-13 18:23 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[18+ messages in thread]
BUG #15895: pg_dump execution with OpenSSL encryption from Windows Service application
2019-07-05 07:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15895: pg_dump execution with OpenSSL encryption from Windows Service application
2019-07-05 13:08 UTC Robert Haas <robertmhaas@gmail.com>
` [PATCH] Don't open partitions that were detached and dropped
2024-08-13 18:07 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[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