pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18796: Npgsql Driver: Foreign Key Read Inversion in INSERT Operations
2025-02-05 20:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18796: Npgsql Driver: Foreign Key Read Inversion in INSERT Operations
2025-02-06 00:06 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
bug report: initdb failure on Microsoft Windows if path to initdb contains special chars
2025-02-04 13:57 UTC Stöcker Bernhard - aktivweb GmbH <bernhard.stoecker@aktivweb.de>
` Re: bug report: initdb failure on Microsoft Windows if path to initdb contains special chars
2025-02-04 15:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 19:19 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 19:24 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 20:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 20:46 UTC Basha <basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 21:18 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 21:24 UTC Christophe Pettus <xof@thebuild.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-06 23:44 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 00:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 00:29 UTC Christophe Pettus <xof@thebuild.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 00:32 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 01:03 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 01:30 UTC Christophe Pettus <xof@thebuild.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 01:40 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 01:48 UTC Christophe Pettus <xof@thebuild.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 02:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 02:19 UTC Christophe Pettus <xof@thebuild.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 02:27 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 14:09 UTC Joe Conway <mail@joeconway.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 14:38 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 15:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 15:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 16:03 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 17:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 17:29 UTC Christophe Pettus <xof@thebuild.com>
` RE: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 17:51 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 18:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-07 18:57 UTC Basha <Basha@maxcontact.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2024-09-09 16:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2025-02-04 14:43 UTC Georgy Artos <georgyartos@gmail.com>
` Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
2025-02-04 14:53 UTC Daniel Gustafsson <daniel@yesql.se>
[30+ messages in thread]
BUG #18789: logical replication slots are deleted after failovers
2025-01-29 12:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18789: logical replication slots are deleted after failovers
2025-01-29 19:13 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: BUG #18789: logical replication slots are deleted after failovers
2025-01-30 11:48 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18789: logical replication slots are deleted after failovers
2025-02-01 05:35 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18789: logical replication slots are deleted after failovers
2025-02-03 13:59 UTC Sachin Konde-Deshmukh <sachinkonde3@gmail.com>
` RE: BUG #18789: logical replication slots are deleted after failovers
2025-02-04 04:20 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[6+ messages in thread]
BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots
2025-02-03 17:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots
2025-02-03 23:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-01-16 10:50 UTC Rajni Bobal <rajnibobal@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-01-16 14:55 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-01-16 15:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-01-22 15:54 UTC Rajni Bobal <rajnibobal@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-01-22 16:43 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-01-23 08:57 UTC Rajni Bobal <rajnibobal@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-01-23 14:24 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-01-23 14:54 UTC Rajni Bobal <rajnibobal@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-01-23 15:02 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-01-23 15:03 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-02-03 05:32 UTC Rajni Bobal <rajnibobal@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-02-03 05:37 UTC Rajni Bobal <rajnibobal@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-02-03 05:50 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4
2025-02-03 11:10 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
[14+ messages in thread]
BUG #18791: Failed installtion during creation of spatial database
2025-02-01 01:45 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18790: Pg_stat_statements doesn't track schema.
2025-01-29 19:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18790: Pg_stat_statements doesn't track schema.
2025-01-30 06:40 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18790: Pg_stat_statements doesn't track schema.
2025-01-30 16:29 UTC Raghvendra Mishra <raghshr1351@gmail.com>
` Re: BUG #18790: Pg_stat_statements doesn't track schema.
2025-01-30 18:01 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #18790: Pg_stat_statements doesn't track schema.
2025-01-31 11:23 UTC Raghvendra Mishra <raghshr1351@gmail.com>
` Re: BUG #18790: Pg_stat_statements doesn't track schema.
2025-01-31 17:50 UTC Greg Sabino Mullane <htamfids@gmail.com>
[6+ messages in thread]
Trying to ugrade from version 16.2 to 17
2025-01-29 14:20 UTC Stanley Pagenel <spagenel@exo.quebec>
` Re: Trying to ugrade from version 16.2 to 17
2025-01-29 16:29 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` RE: Trying to ugrade from version 16.2 to 17
2025-01-30 10:46 UTC Stanley Pagenel <spagenel@exo.quebec>
[3+ messages in thread]
BUG #18784: Bugs and BugTracking
2025-01-24 05:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18784: Bugs and BugTracking
2025-01-24 18:25 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18784: Bugs and BugTracking
2025-01-24 19:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18784: Bugs and BugTracking
2025-01-28 09:56 UTC VASUKI M <vasukim1992002@gmail.com>
` Fwd: BUG #18784: Bugs and BugTracking
2025-01-30 03:59 UTC VASUKI M <vasukim1992002@gmail.com>
[5+ messages in thread]
BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-05 02:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-05 18:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 04:12 UTC Koichi Suzuki <koichi.dbms@gmail.com>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 05:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 05:21 UTC Tatsuo Ishii <ishii@postgresql.org>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 05:26 UTC Koichi Suzuki <koichi.dbms@gmail.com>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 05:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 05:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 06:11 UTC Koichi Suzuki <koichi.dbms@gmail.com>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 06:13 UTC Koichi Suzuki <koichi.dbms@gmail.com>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 06:29 UTC Tatsuo Ishii <ishii@postgresql.org>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 06:42 UTC Tatsuo Ishii <ishii@postgresql.org>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 18:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 20:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-06 23:14 UTC Tatsuo Ishii <ishii@postgresql.org>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-07 00:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-08 10:37 UTC Tatsuo Ishii <ishii@postgresql.org>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-08 11:01 UTC Tatsuo Ishii <ishii@postgresql.org>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2024-12-08 22:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2025-01-28 06:34 UTC Koichi Suzuki <koichi.suzuki@enterprisedb.com>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2025-01-28 07:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2025-01-28 07:28 UTC Koichi Suzuki <koichi.dbms@gmail.com>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2025-01-29 19:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
2025-01-29 23:39 UTC Koichi Suzuki <koichi.dbms@gmail.com>
[24+ messages in thread]
BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-01-28 13:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-01-28 19:55 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-01-28 20:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-01-28 20:12 UTC Andres Freund <andres@anarazel.de>
[4+ messages in thread]
BUG #18787: pointer te->defn not checked for NULL
2025-01-28 14:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18787: pointer te->defn not checked for NULL
2025-01-28 15:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18786: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-01-28 14:08 UTC PG Bug reporting form <noreply@postgresql.org>
Re: reltuples kept decreasing with each autovacuum run Re: BUG #18773: $B%*!<(B$B%H%P%-%e!<%`$N%j%H%i%$;~$K(Breltuples$B$NCM$,8:>/$9$k(B
2025-01-21 02:13 UTC $BM&<!(B $B0BF#(B <antengynnnn536@gmail.com>
` Re: reltuples kept decreasing with each autovacuum run Re: BUG #18773: $B%*!<(B$B%H%P%-%e!<%`$N%j%H%i%$;~$K(Breltuples$B$NCM$,8:>/$9$k(B
2025-01-28 07:41 UTC $B0BF#M&<!(B <antengynnnn536@gmail.com>
[2+ messages in thread]
Evidence of Ownership Issues During Restoration of Extension Member Objects
2025-01-28 05:29 UTC AKASH <akashbhujbal7051@gmail.com>
` Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
2025-01-28 05:47 UTC Christophe Pettus <xof@thebuild.com>
` Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
2025-01-28 05:56 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
2025-01-28 06:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
2025-01-28 06:46 UTC AKASH <akashbhujbal7051@gmail.com>
[5+ messages in thread]
PostgreSQL 17.2 servers crashing due to segmentation faults on query execution
2025-01-27 14:55 UTC Victor Castro Amigo <vcastro@AVALONINFORMATICA.COM>
` Re: PostgreSQL 17.2 servers crashing due to segmentation faults on query execution
2025-01-27 16:06 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
Superuser can't revoke role granted by non-superuser
2025-01-27 08:49 UTC Alexander Kukushkin <cyberdemn@gmail.com>
` Re: Superuser can't revoke role granted by non-superuser
2025-01-27 09:20 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Superuser can't revoke role granted by non-superuser
2025-01-27 09:22 UTC Alexander Kukushkin <cyberdemn@gmail.com>
` Re: Superuser can't revoke role granted by non-superuser
2025-01-27 09:37 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Superuser can't revoke role granted by non-superuser
2025-01-27 10:13 UTC Alexander Kukushkin <cyberdemn@gmail.com>
` Re: Superuser can't revoke role granted by non-superuser
2025-01-27 14:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
BUG #18782: Inconsistent behaviour with triggers and row level security - depends on prior number of inserts
2025-01-21 15:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18782: Inconsistent behaviour with triggers and row level security - depends on prior number of inserts
2025-01-25 19:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18782: Inconsistent behaviour with triggers and row level security - depends on prior number of inserts
2025-01-27 09:45 UTC Julian Wreford <julian.wreford@gearset.com>
[3+ messages in thread]
Parent index on partitioned table could still be invalid even when children are not
2025-01-23 19:09 UTC Dmytro Astapov <dastapov@gmail.com>
` Re: Parent index on partitioned table could still be invalid even when children are not
2025-01-24 12:57 UTC Dmytro Astapov <dastapov@gmail.com>
[2+ messages in thread]
BUG #18783: 2025-01-23 03:55:06.243 GMT [22929] LOG: postmaster became multithreaded 2025-01-23 03:55:06.243 GM
2025-01-23 04:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18783: 2025-01-23 03:55:06.243 GMT [22929] LOG: postmaster became multithreaded 2025-01-23 03:55:06.243 GM
2025-01-23 18:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18779: Segmentation fault while trying to connect via psql
2025-01-17 11:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18779: Segmentation fault while trying to connect via psql
2025-01-19 02:32 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #18779: Segmentation fault while trying to connect via psql
2025-01-22 08:28 UTC Даниил Элишаков <dan-eli@mail.ru>
[3+ messages in thread]
Combining array slicing and indexing causes incorrect/confusing results
2025-01-21 16:35 UTC Jelte Fennema-Nio <me@jeltef.nl>
` Re: Combining array slicing and indexing causes incorrect/confusing results
2025-01-21 17:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
回复：Re: Performance Issue when using gin index
2025-01-21 06:25 UTC 谭忠涛 <zhongtao.tan@seaboxdata.com>
Performance Issue when using gin index
2025-01-21 02:30 UTC 谭忠涛 <zhongtao.tan@seaboxdata.com>
` Re: Performance Issue when using gin index
2025-01-21 03:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
[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