pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedcom/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]
BUG #18745: /src/bin/pg_waldump/compat.c
2024-12-09 13:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18745: /src/bin/pg_waldump/compat.c
2024-12-11 21:18 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
postgres 16 index double variable seems to fail. postgres 15 OK
2024-12-10 13:18 UTC Vladislav Malyshkin <mal@gromco.com>
` Re: postgres 16 index double variable seems to fail. postgres 15 OK
2024-12-10 14:30 UTC Euler Taveira <euler@eulerto.com>
[2+ messages in thread]
BUG #18585: Date/time conversion functions are not protected against integer overflow
2024-08-17 15:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18585: Date/time conversion functions are not protected against integer overflow
2024-08-17 16:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18585: Date/time conversion functions are not protected against integer overflow
2024-08-18 17:02 UTC Joseph Koshakow <koshy44@gmail.com>
` Re: BUG #18585: Date/time conversion functions are not protected against integer overflow
2024-12-09 20:00 UTC Nathan Bossart <nathandbossart@gmail.com>
[4+ messages in thread]
BUG #18743: /src/backend/rewrite/rewriteHandler.c
2024-12-09 11:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18743: /src/backend/rewrite/rewriteHandler.c
2024-12-09 18:37 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
BUG #18742: /src/backend/rewrite/rewriteHandler.c
2024-12-09 11:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18742: /src/backend/rewrite/rewriteHandler.c
2024-12-09 15:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18746: /src/backend/parser/parse_utilcmd.c
2024-12-09 13:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18746: /src/backend/parser/parse_utilcmd.c
2024-12-09 14:33 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[2+ messages in thread]
BUG #10123: Weird entries in pg_stat_activity
2014-04-24 10:18 UTC maxim.boguk@gmail.com
` Re: BUG #10123: Weird entries in pg_stat_activity
2014-04-24 10:26 UTC Magnus Hagander <magnus@hagander.net>
` Re: BUG #10123: Weird entries in pg_stat_activity
2014-04-24 10:44 UTC Andres Freund <andres@2ndquadrant.com>
` Re: BUG #10123: Weird entries in pg_stat_activity
2014-04-24 10:48 UTC Magnus Hagander <magnus@hagander.net>
` Re: BUG #10123: Weird entries in pg_stat_activity
2014-04-24 11:05 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #10123: Weird entries in pg_stat_activity
2014-04-24 16:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #10123: Weird entries in pg_stat_activity
2014-04-24 17:46 UTC Andres Freund <andres@2ndquadrant.com>
` Re: BUG #10123: Weird entries in pg_stat_activity
2014-04-24 18:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #10123: Weird entries in pg_stat_activity
2014-04-25 01:04 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #10123: Weird entries in pg_stat_activity
2014-05-25 09:40 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: [BUGS] BUG #10123: Weird entries in pg_stat_activity
2024-07-03 15:14 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: [BUGS] BUG #10123: Weird entries in pg_stat_activity
2024-07-04 05:54 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: [BUGS] BUG #10123: Weird entries in pg_stat_activity
2024-07-04 22:03 UTC Andres Freund <andres@anarazel.de>
` Re: [BUGS] BUG #10123: Weird entries in pg_stat_activity
2024-10-16 16:59 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: [BUGS] BUG #10123: Weird entries in pg_stat_activity
2024-10-17 04:19 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: [BUGS] BUG #10123: Weird entries in pg_stat_activity
2024-11-22 14:54 UTC Maxim Orlov <orlovmg@gmail.com>
` Re: [BUGS] BUG #10123: Weird entries in pg_stat_activity
2024-12-09 14:27 UTC Tomas Vondra <tomas@vondra.me>
[17+ messages in thread]
BUG #18744: /src/bin/pg_dump/pg_backup_archiver.c
2024-12-09 11:27 UTC PG Bug reporting form <noreply@postgresql.org>
FF3 vs MS Date/Time Template - ERROR: date/time field value out of range
2024-12-06 12:44 UTC Nick Davies <Nick.Davies@iliad-solutions.com>
` Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range
2024-12-07 17:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range
2024-12-09 09:16 UTC Nick Davies <Nick.Davies@iliad-solutions.com>
[3+ messages in thread]
[Bug] Heap Use After Free in Window Aggregate Execution
2024-11-13 15:22 UTC Jayesh Dehankar <jayesh.dp@zohocorp.com>
` Re: [Bug] Heap Use After Free in Window Aggregate Execution
2024-12-05 17:08 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: [Bug] Heap Use After Free in Window Aggregate Execution
2024-12-05 20:21 UTC David Rowley <dgrowleyml@gmail.com>
` Re: [Bug] Heap Use After Free in Window Aggregate Execution
2024-12-09 01:28 UTC David Rowley <dgrowleyml@gmail.com>
[4+ messages in thread]
Dangling operator family after DROP TYPE
2024-12-06 15:15 UTC Yoran Heling <contact@yorhel.nl>
` Re: Dangling operator family after DROP TYPE
2024-12-06 17:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Dangling operator family after DROP TYPE
2024-12-06 18:36 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Dangling operator family after DROP TYPE
2024-12-06 22:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Install postgres 14 on SLES 15 SP1
2024-12-06 08:17 UTC KALLIOPI DIMOKA <Kalliopi.Dimoka@kyndryl.com>
` Re: Install postgres 14 on SLES 15 SP1
2024-12-06 13:21 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
2024-12-04 23:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
2024-12-05 18:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
2024-12-05 20:13 UTC Andres Freund <andres@anarazel.de>
[3+ messages in thread]
Tablespace storage bug...
2024-12-05 01:04 UTC Greg Kemnitz <gjkemnitz@gmail.com>
` Re: Tablespace storage bug...
2024-12-05 01:09 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Tablespace storage bug...
2024-12-05 02:12 UTC Greg Kemnitz <gjkemnitz@gmail.com>
[3+ messages in thread]
[Bug] Heap Use After Free in parallel_vacuum_reset_dead_items Function
2024-11-25 18:27 UTC Vallimaharajan G <vallimaharajan.gs@zohocorp.com>
` Re: [Bug] Heap Use After Free in parallel_vacuum_reset_dead_items Function
2024-11-26 09:53 UTC John Naylor <johncnaylorls@gmail.com>
` Re: [Bug] Heap Use After Free in parallel_vacuum_reset_dead_items Function
2024-12-05 01:46 UTC John Naylor <johncnaylorls@gmail.com>
[3+ messages in thread]
Issue with pg_dump Including Ownership Metadata for pg_trgm Extension in PostgreSQL 17
2024-12-04 09:42 UTC AKASH <akashbhujbal7051@gmail.com>
` Re: Issue with pg_dump Including Ownership Metadata for pg_trgm Extension in PostgreSQL 17
2024-12-04 09:43 UTC AKASH <akashbhujbal7051@gmail.com>
` Re: Issue with pg_dump Including Ownership Metadata for pg_trgm Extension in PostgreSQL 17
2024-12-04 16:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18731: The psql \d command does not exactly match but can be executed
2024-12-03 09:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18731: The psql \d command does not exactly match but can be executed
2024-12-03 17:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18731: The psql \d command does not exactly match but can be executed
2024-12-04 02:50 UTC zengman <zengman@halodbtech.com>
[3+ messages in thread]
BUG #18733: Connection Timeout after upgrade
2024-12-03 15:42 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18732: Segfault in pgbench on max_connections starvation
2024-12-03 12:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18732: Segfault in pgbench on max_connections starvation
2024-12-03 14:52 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18732: Segfault in pgbench on max_connections starvation
2024-12-03 15:27 UTC Andres Freund <andres@anarazel.de>
[3+ messages in thread]
BUG #18730: Inequality comparison operators and SMALLINT negative immediate value
2024-12-03 01:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18730: Inequality comparison operators and SMALLINT negative immediate value
2024-12-03 13:48 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ 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