pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18704: Installing postgis fails due to depencies
2024-11-13 15:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18704: Installing postgis fails due to depencies
2024-12-30 19:40 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #18758: Incorrect query result caused by ROLLUP operation
2024-12-30 16:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18758: Incorrect query result caused by ROLLUP operation
2024-12-30 19:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
pg_upgrade cannot create btrfs clones on linux kernel 6.8.0
2024-12-30 00:36 UTC Michael Misiewicz <mmisiewicz@hey.com>
` Re: pg_upgrade cannot create btrfs clones on linux kernel 6.8.0
2024-12-30 02:12 UTC Tomas Vondra <tomas@vondra.me>
` Re: pg_upgrade cannot create btrfs clones on linux kernel 6.8.0
2024-12-30 18:55 UTC Michael Misiewicz <mmisiewicz@hey.com>
[3+ messages in thread]
BUG #18756: Postgres corruption
2024-12-29 18:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18756: Postgres corruption
2024-12-29 23:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18755: Using Natts_pg_trigger rather than Natts_pg_event_trigger for event trigger
2024-12-29 08:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18755: Using Natts_pg_trigger rather than Natts_pg_event_trigger for event trigger
2024-12-29 09:37 UTC 张鑫 <zhanghien@qq.com>
` Re: BUG #18755: Using Natts_pg_trigger rather than Natts_pg_event_trigger for event trigger
2024-12-29 10:36 UTC David Rowley <dgrowleyml@gmail.com>
[3+ messages in thread]
BUG #18753: Unable to Recover a Deleted Database Using PITR
2024-12-24 04:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18753: Unable to Recover a Deleted Database Using PITR
2024-12-27 02:44 UTC px shi <spxlyy123@gmail.com>
[2+ messages in thread]
BUG #18750: Inappropriate update when it is blocked in RC
2024-12-23 06:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18750: Inappropriate update when it is blocked in RC
2024-12-24 12:37 UTC Pantelis Theodosiou <ypercube@gmail.com>
` Re: BUG #18750: Inappropriate update when it is blocked in RC
2024-12-24 17:24 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: Re: BUG #18750: Inappropriate update when it is blocked in RC
2024-12-25 05:31 UTC yrshen@stu.xidian.edu.cn
` Re: Re: BUG #18750: Inappropriate update when it is blocked in RC
2024-12-25 05:32 UTC yrshen@stu.xidian.edu.cn
` Re: Re: BUG #18750: Inappropriate update when it is blocked in RC
2024-12-25 05:57 UTC yrshen@stu.xidian.edu.cn
` Re: Re: BUG #18750: Inappropriate update when it is blocked in RC
2024-12-25 12:46 UTC Pantelis Theodosiou <ypercube@gmail.com>
` Re: Re: Re: BUG #18750: Inappropriate update when it is blocked in RC
2024-12-26 09:47 UTC yrshen@stu.xidian.edu.cn
[8+ messages in thread]
psql v16.3 successfully connects via TLSv1.3 proxy, but psql v16.4 says "tlsv1 alert no application protocol"
2024-12-25 17:05 UTC Markus KARG <markus@headcrashing.eu>
` Re: psql v16.3 successfully connects via TLSv1.3 proxy, but psql v16.4 says "tlsv1 alert no application protocol"
2024-12-25 17:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: psql v16.3 successfully connects via TLSv1.3 proxy, but psql v16.4 says "tlsv1 alert no application protocol"
2024-12-25 17:45 UTC Markus KARG <markus@headcrashing.eu>
` Re: psql v16.3 successfully connects via TLSv1.3 proxy, but psql v16.4 says "tlsv1 alert no application protocol"
2024-12-25 17:52 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: psql v16.3 successfully connects via TLSv1.3 proxy, but psql v16.4 says "tlsv1 alert no application protocol"
2024-12-25 18:22 UTC Markus KARG <markus@headcrashing.eu>
` Re: psql v16.3 successfully connects via TLSv1.3 proxy, but psql v16.4 says "tlsv1 alert no application protocol"
2024-12-25 18:52 UTC Markus KARG <markus@headcrashing.eu>
` Re: psql v16.3 successfully connects via TLSv1.3 proxy, but psql v16.4 says "tlsv1 alert no application protocol"
2024-12-25 19:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: psql v16.3 successfully connects via TLSv1.3 proxy, but psql v16.4 says "tlsv1 alert no application protocol"
2024-12-25 22:47 UTC Markus KARG <markus@headcrashing.eu>
[8+ messages in thread]
Corrupt index lead to skipped autovacuum
2024-12-24 05:43 UTC 高偉鈞 <weichun@bebit-tech.com>
` Re: Corrupt index lead to skipped autovacuum
2024-12-25 15:43 UTC Tomas Vondra <tomas@vondra.me>
[2+ messages in thread]
BUG #18751: Sub-optimal UNION ALL plan
2024-12-23 09:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18751: Sub-optimal UNION ALL plan
2024-12-23 14:24 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #18751: Sub-optimal UNION ALL plan
2024-12-23 15:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18751: Sub-optimal UNION ALL plan
2024-12-24 02:57 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18751: Sub-optimal UNION ALL plan
2024-12-24 03:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18751: Sub-optimal UNION ALL plan
2024-12-24 09:05 UTC Andrei Lepikhov <lepihov@gmail.com>
[6+ messages in thread]
Commit 5a2fed911a broke parallel query
2024-12-23 10:55 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Commit 5a2fed911a broke parallel query
2024-12-23 15:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Commit 5a2fed911a broke parallel query
2024-12-23 17:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Commit 5a2fed911a broke parallel query
2024-12-23 17:39 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[4+ messages in thread]
BUG #18749: Error Installing PostgreSQL
2024-12-20 19:46 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18748: Old name version
2024-12-20 06:09 UTC PG Bug reporting form <noreply@postgresql.org>
Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-17 02:54 UTC Sam James <sam@gentoo.org>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-17 18:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-17 19:30 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-17 20:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-17 21:18 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-17 21:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-17 22:45 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-17 22:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-18 01:30 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-18 01:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-20 08:35 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-20 15:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-21 07:23 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-25 10:01 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-25 15:57 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-25 19:51 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-25 20:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-26 02:03 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-26 02:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-26 02:25 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-26 11:24 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-27 04:50 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-27 09:27 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-27 14:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-27 18:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-27 18:50 UTC Andres Freund <andres@anarazel.de>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-27 19:01 UTC Sam James <sam@gentoo.org>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-27 19:21 UTC Andres Freund <andres@anarazel.de>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-27 19:32 UTC Andres Freund <andres@anarazel.de>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-29 06:26 UTC Robins Tharakan <tharakan@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-11-29 15:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-07 11:42 UTC Robins Tharakan <tharakan@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-13 01:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-13 02:01 UTC Robins Tharakan <tharakan@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-13 02:16 UTC Robins Tharakan <tharakan@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-13 02:31 UTC Robins Tharakan <tharakan@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-13 03:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-13 13:48 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-14 10:46 UTC Robins Tharakan <tharakan@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-14 17:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-15 07:04 UTC Robins Tharakan <tharakan@gmail.com>
` Re: Build failure with GCC 15 (defaults to -std=gnu23)
2024-12-19 02:45 UTC Thomas Munro <thomas.munro@gmail.com>
[42+ messages in thread]
Not able to restore database - error: could not decompress data: Allocation error : not enough memory
2024-12-17 20:29 UTC Tomasz Szypowski <tomasz.szypowski@asseco.pl>
` Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory
2024-12-18 02:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: Not able to restore database - error: could not decompress data: Allocation error : not enough memory
2024-12-18 07:12 UTC Tomasz Szypowski <tomasz.szypowski@asseco.pl>
` Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory
2024-12-18 15:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Incompatibility of newest pg_restore with PostgreSQL-Servers older or equal to version 16
2024-12-18 10:05 UTC combit - Nicolaij Deutschkämer <Deutschkaemer@combit.net>
` Re: Incompatibility of newest pg_restore with PostgreSQL-Servers older or equal to version 16
2024-12-18 14:25 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
Surprising SeqScan of appendRel that can't contribute any rows to the result
2024-12-17 22:15 UTC Dmytro Astapov <dastapov@gmail.com>
` Re: Surprising SeqScan of appendRel that can't contribute any rows to the result
2024-12-18 00:08 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Surprising SeqScan of appendRel that can't contribute any rows to the result
2024-12-18 00:36 UTC Dmytro Astapov <dastapov@gmail.com>
` Re: Surprising SeqScan of appendRel that can't contribute any rows to the result
2024-12-18 01:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Is it possible to make ReorderBufferRestoreCleanup faster?
2024-12-17 18:01 UTC Evgeny Kuzin <evgeny.kuzin@outlook.com>
to_timestamp function calculation error
2024-12-17 11:51 UTC myzhen <zhenmingyang@yeah.net>
` Re: to_timestamp function calculation error
2024-12-17 15:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
"memory exhausted" in query parser/simplifier for many nested parentheses
2024-12-11 21:59 UTC Niklas Hambüchen <mail@nh2.me>
` Re: "memory exhausted" in query parser/simplifier for many nested parentheses
2024-12-12 12:39 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: "memory exhausted" in query parser/simplifier for many nested parentheses
2024-12-12 16:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: "memory exhausted" in query parser/simplifier for many nested parentheses
2024-12-12 16:46 UTC Niklas Hambüchen <mail@nh2.me>
` Re: "memory exhausted" in query parser/simplifier for many nested parentheses
2024-12-13 14:44 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: "memory exhausted" in query parser/simplifier for many nested parentheses
2024-12-13 15:11 UTC Tomas Vondra <tomas@vondra.me>
` Re: "memory exhausted" in query parser/simplifier for many nested parentheses
2024-12-13 16:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: "memory exhausted" in query parser/simplifier for many nested parentheses
2024-12-13 17:06 UTC Niklas Hambüchen <mail@nh2.me>
` Re: "memory exhausted" in query parser/simplifier for many nested parentheses
2024-12-13 17:43 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: "memory exhausted" in query parser/simplifier for many nested parentheses
2024-12-13 22:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
[10+ messages in thread]
com/ongres/scram/common/exception/ScramException prevents use of postgresql-42.7.2.jar with scram-sha-256
2024-12-13 12:56 UTC David Gradwell <david@gradwell.com>
` Re: com/ongres/scram/common/exception/ScramException prevents use of postgresql-42.7.2.jar with scram-sha-256
2024-12-13 13:03 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: com/ongres/scram/common/exception/ScramException prevents use of postgresql-42.7.2.jar with scram-sha-256
2024-12-13 14:26 UTC Dave Cramer <davecramer@postgres.rocks>
[3+ messages in thread]
BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-16 00:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-17 18:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-19 18:48 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-19 19:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-19 22:50 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-19 23:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 03:47 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 04:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 08:17 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 15:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 15:20 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 15:32 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 15:35 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 15:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 15:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 16:02 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 16:02 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 16:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 16:50 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-20 22:36 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-21 07:27 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-21 14:21 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-21 14:35 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-21 14:47 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-21 15:14 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-21 16:44 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-21 17:09 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-21 18:05 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-21 18:14 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-22 00:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-22 04:39 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-22 04:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-22 07:45 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-22 19:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-22 20:01 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-22 20:06 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-22 20:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-22 20:17 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-23 08:37 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-23 09:50 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-23 17:50 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-27 15:40 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-27 16:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-27 16:36 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-27 16:50 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-27 17:43 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-27 17:50 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-27 18:03 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-27 18:12 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-27 18:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-27 19:34 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-28 08:12 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-28 12:22 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-28 16:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-28 21:12 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-11-29 10:15 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-02 05:39 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-02 23:00 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-02 23:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-02 23:37 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-03 01:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-03 07:38 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-03 08:03 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-11 20:59 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-11 21:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-11 22:39 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
2024-12-12 21:55 UTC Nathan Bossart <nathandbossart@gmail.com>
[67+ messages in thread]
Problem with constraint unique.
2024-12-11 14:47 UTC Марат Гасанян <marat_gasanyan@mail.ru>
` Re: Problem with constraint unique.
2024-12-12 06:47 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Problem with constraint unique.
2024-12-12 17:52 UTC Mani Sankar <manisankar01695@gmail.com>
` Re: Problem with constraint unique.
2024-12-12 18:34 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: Problem with constraint unique.
2024-12-12 18:44 UTC Mani Sankar <manisankar01695@gmail.com>
[5+ messages in thread]
invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
2024-12-12 14:08 UTC Mike Bayer <mike_mp@zzzcomputing.com>
` Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
2024-12-12 14:14 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
2024-12-12 14:27 UTC jian he <jian.universality@gmail.com>
` Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
2024-12-12 14:31 UTC jian he <jian.universality@gmail.com>
` Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
2024-12-12 14:37 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
2024-12-12 14:55 UTC Mike Bayer <mike_mp@zzzcomputing.com>
` Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
2024-12-12 15:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: invalid constraint type "n" when using pg_catalog.pg_get_constraintdef() on pg17, regression from pg16
2024-12-12 15:59 UTC Mike Bayer <mike_mp@zzzcomputing.com>
[8+ messages in thread]
pg_dump crash on identity sequence with not loaded attributes
2024-12-09 15:54 UTC Artur Zakirov <zaartur@gmail.com>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-09 21:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-10 15:21 UTC Artur Zakirov <zaartur@gmail.com>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-10 15:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-10 15:34 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-10 17:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-10 17:54 UTC Artur Zakirov <zaartur@gmail.com>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-10 18:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-10 18:40 UTC Artur Zakirov <zaartur@gmail.com>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-10 21:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-11 11:38 UTC Artur Zakirov <zaartur@gmail.com>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-11 15:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump crash on identity sequence with not loaded attributes
2024-12-11 21:41 UTC Artur Zakirov <zaartur@gmail.com>
[13+ 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