pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #19448: message There has been an error  a debug file been created at installbuilder_debug_18008.xml
  2026-03-31 14:53 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19443: GIN jsonb_path_ops index not used when many rows contain nested null values (PostgreSQL 18.3)
  2026-03-30 03:09 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19443: GIN jsonb_path_ops index not used when many rows contain nested null values (PostgreSQL 18.3)
  2026-03-30 19:03 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #19446: Domain DEFAULT not reflected in system catalogs and information_schema  (PG 18.3)
  2026-03-30 03:12 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19446: Domain DEFAULT not reflected in system catalogs and information_schema (PG 18.3)
  2026-03-30 15:00 UTC  Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #19446: Domain DEFAULT not reflected in system catalogs and information_schema (PG 18.3)
  2026-03-30 18:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #19445: Domain DEFAULT not recorded in pg_attrdef (atthasdef false) in PostgreSQL 18.3
  2026-03-30 03:11 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19445: Domain DEFAULT not recorded in pg_attrdef (atthasdef false) in PostgreSQL 18.3
  2026-03-30 14:56 UTC  Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #19445: Domain DEFAULT not recorded in pg_attrdef (atthasdef false) in PostgreSQL 18.3
  2026-03-30 18:49 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #19444: conkey field empty for domain NOT NULL constraint in pg_constraint (18.3)
  2026-03-30 03:10 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19444: conkey field empty for domain NOT NULL constraint in pg_constraint (18.3)
  2026-03-30 14:17 UTC  Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #19444: conkey field empty for domain NOT NULL constraint in pg_constraint (18.3)
  2026-03-30 18:44 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-25 13:27 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-27 01:02 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-27 17:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-29 08:43 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-29 15:32 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-29 16:25 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-29 23:33 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-29 23:41 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-29 23:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-30 00:15 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-30 00:34 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-30 01:09 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-30 02:19 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19438: segfault with temp_file_limit inside cursor
  2026-03-30 16:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [14+ messages in thread]

BUG #19442: PL/pgSQL: domain over composite type bypasses type validation when assigning NULL (PostgreSQL 18.3)
  2026-03-30 03:09 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19442: PL/pgSQL: domain over composite type bypasses type validation when assigning NULL (PostgreSQL 18.3)
  2026-03-30 14:39 UTC  Junwang Zhao <zhjwpku@gmail.com>
  [2+ messages in thread]

Memory leak in pg_stat_statements when qtext file contains invalid encoding
  2026-03-27 07:54 UTC  Gaurav Singh <gaurav.singh@yugabyte.com>
` Memory leak in pg_stat_statements when query text file contains invalid encoding
  2026-03-27 08:03 UTC  Gaurav Singh <gaurav.singh@yugabyte.com>
` Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
  2026-03-27 08:21 UTC  Lukas Fittl <lukas@fittl.com>
` Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
  2026-03-27 08:49 UTC  Gaurav Singh <gaurav.singh@yugabyte.com>
` Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
  2026-03-27 08:51 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
  2026-03-27 08:57 UTC  Gaurav Singh <gaurav.singh@yugabyte.com>
` Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
  2026-03-27 08:59 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
  2026-03-27 09:05 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
  2026-03-27 11:13 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
  2026-03-27 15:25 UTC  Lukas Fittl <lukas@fittl.com>
  [10+ messages in thread]

POSTGIS | SQL Error [42501]: ERROR: permission denied to create "pg_catalog.geometry_dump"
  2026-03-26 20:38 UTC  Sérgio Duarte <duartes@gmail.com>
` Re: POSTGIS | SQL Error [42501]: ERROR: permission denied to create "pg_catalog.geometry_dump"
  2026-03-26 21:07 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: POSTGIS | SQL Error [42501]: ERROR: permission denied to create "pg_catalog.geometry_dump"
  2026-03-27 11:05 UTC  Sérgio Duarte <duartes@gmail.com>
  [3+ messages in thread]

BUG #19440: Memory leak in pg_stat_statements when query text file contains invalid encoding
  2026-03-27 08:10 UTC  PG Bug reporting form <noreply@postgresql.org>

Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE CONCURRENTLY
  2026-03-18 09:54 UTC  Ana Almeida <Ana.Almeida@timestamp.pt>
` Re: Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE CONCURRENTLY
  2026-03-18 13:10 UTC  Jim Jones <jim.jones@uni-muenster.de>
` RE: Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE CONCURRENTLY
  2026-03-18 14:54 UTC  Ana Almeida <Ana.Almeida@timestamp.pt>
` Re: Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE CONCURRENTLY
  2026-03-18 23:42 UTC  Tomas Vondra <tomas@vondra.me>
` RE: Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE CONCURRENTLY
  2026-03-20 12:26 UTC  Ana Almeida <Ana.Almeida@timestamp.pt>
` Re: Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE CONCURRENTLY
  2026-03-26 23:44 UTC  Michael Paquier <michael@paquier.xyz>
  [6+ messages in thread]

Re: Re: Revoke Connect Privilege from Database not working
  2025-04-07 13:42 UTC  David G. Johnston <david.g.johnston@gmail.com>
`  Re:   Re: Re: Revoke Connect Privilege from Database not working
  2025-04-07 15:37 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re:   Re: Re: Revoke Connect Privilege from Database not working
  2025-04-07 16:06 UTC  Tom Lane <tgl@sss.pgh.pa.us>
`  Re:   Re: Re: Revoke Connect Privilege from Database not working
  2025-04-07 16:22 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re:   Re: Re: Revoke Connect Privilege from Database not working
  2025-11-13 16:47 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: Revoke Connect Privilege from Database not working
  2026-01-20 23:05 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Revoke Connect Privilege from Database not working
  2026-01-21 15:28 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: Revoke Connect Privilege from Database not working
  2026-01-21 16:57 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Revoke Connect Privilege from Database not working
  2026-03-06 22:01 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: Revoke Connect Privilege from Database not working
  2026-03-18 00:50 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: Revoke Connect Privilege from Database not working
  2026-03-18 16:36 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Revoke Connect Privilege from Database not working
  2026-03-18 17:47 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: Revoke Connect Privilege from Database not working
  2026-03-18 17:58 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Revoke Connect Privilege from Database not working
  2026-03-19 16:44 UTC  Nathan Bossart <nathandbossart@gmail.com>
  [14+ messages in thread]

BUG #19436: Azure Arc installation failure
  2026-03-17 13:30 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19436: Azure Arc installation failure
  2026-03-17 16:11 UTC  Magnus Hagander <magnus@hagander.net>
` RE: BUG #19436: Azure Arc installation failure
  2026-03-17 17:46 UTC  Devey, Richard <richard.devey@treehousefoods.com>
` Re: BUG #19436: Azure Arc installation failure
  2026-03-19 02:23 UTC  John Naylor <johncnaylorls@gmail.com>
  [4+ messages in thread]

ALTER FOREIGN DATA WRAPPER can drop dependency on handler
  2026-03-18 19:09 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: ALTER FOREIGN DATA WRAPPER can drop dependency on handler
  2026-03-18 19:29 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: ALTER FOREIGN DATA WRAPPER can drop dependency on handler
  2026-03-18 20:40 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: ALTER FOREIGN DATA WRAPPER can drop dependency on handler
  2026-03-18 21:41 UTC  Nathan Bossart <nathandbossart@gmail.com>
  [4+ messages in thread]

Regarding issue in psqlODBC installation
  2026-03-18 06:34 UTC  EXI-Saifuddin, Tagala <tagala.saifuddin@boeing.com>

[PATCH v4 1/1] Allow choosing specific grantors via GRANT/REVOKE ... GRANTED BY.
  2026-03-18 00:40 UTC  Nathan Bossart <nathan@postgresql.org>
` [PATCH v3 1/1] Allow choosing specific grantors via GRANT/REVOKE ... GRANTED BY.
  2026-03-18 00:40 UTC  Nathan Bossart <nathan@postgresql.org>
  [2+ messages in thread]

BUG #19432: recovery fails at invalid checkpoint record
  2026-03-12 16:20 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19432: recovery fails at invalid checkpoint record
  2026-03-12 19:29 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19432: recovery fails at invalid checkpoint record
  2026-03-13 08:35 UTC  Felix Hamme <felix.hamme@ionos.com>
` Re: BUG #19432: recovery fails at invalid checkpoint record
  2026-03-13 16:37 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19432: recovery fails at invalid checkpoint record
  2026-03-16 13:56 UTC  Felix Hamme <felix.hamme@ionos.com>
` Re: BUG #19432: recovery fails at invalid checkpoint record
  2026-03-16 15:07 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [6+ messages in thread]

BUG #19429: An issue regarding the processing of Oid as an int type in ecpg
  2026-03-12 06:31 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19429: An issue regarding the processing of Oid as an int type in ecpg
  2026-03-15 23:00 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #19433: json_object_agg_unique Crashes When Used as Window Function
  2026-03-13 03:14 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19433: json_object_agg_unique Crashes When Used as Window Function
  2026-03-13 10:41 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #19433: json_object_agg_unique Crashes When Used as Window Function
  2026-03-15 21:27 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

Create unique GiST indexes
  2025-12-31 22:55 UTC  Paul A Jungwirth <pj@illuminatedcomputing.com>
` Re: Create unique GiST indexes
  2026-01-02 07:19 UTC  Kirill Reshke <reshkekirill@gmail.com>
` Re: Create unique GiST indexes
  2026-01-02 18:39 UTC  Paul A Jungwirth <pj@illuminatedcomputing.com>
` Re: Create unique GiST indexes
  2026-03-13 20:29 UTC  Paul A Jungwirth <pj@illuminatedcomputing.com>
  [4+ messages in thread]

BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-01 19:05 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-02 05:21 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-03 04:18 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-03 17:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-05 04:52 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-05 09:47 UTC  Jim Jones <jim.jones@uni-muenster.de>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-05 14:15 UTC  Jim Jones <jim.jones@uni-muenster.de>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-06 05:54 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-06 10:22 UTC  Jim Jones <jim.jones@uni-muenster.de>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-08 02:19 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-08 08:33 UTC  Jim Jones <jim.jones@uni-muenster.de>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-08 15:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-08 17:00 UTC  Jim Jones <jim.jones@uni-muenster.de>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-06-08 22:27 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-07-01 06:49 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-07-08 09:49 UTC  Robin Haberkorn <haberkorn@b1-systems.de>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-07-08 11:23 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-07-08 13:36 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-07-09 00:45 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL
  2025-07-09 11:28 UTC  Robin Haberkorn <haberkorn@b1-systems.de>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' isdereferenced at xpath.c:177 without checking for NUL
  2026-03-08 14:12 UTC  =?utf-8?B?Y2NhNTUwNw==?= <cca5507@qq.com>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' isdereferenced at xpath.c:177 without checking for NUL
  2026-03-08 15:05 UTC  =?utf-8?B?Y2NhNTUwNw==?= <cca5507@qq.com>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' isdereferenced at xpath.c:177 without checking for NUL
  2026-03-09 07:31 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' isdereferenced at xpath.c:177 without checking for NUL
  2026-03-09 22:10 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' isdereferenced at xpath.c:177 without checking for NUL
  2026-03-12 05:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' isdereferenced at xpath.c:177 without checking for NUL
  2026-03-12 06:46 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18943: Return value of a function 'xmlBufferCreate' isdereferenced at xpath.c:177 without checking for NUL
  2026-03-13 07:12 UTC  Michael Paquier <michael@paquier.xyz>
  [27+ messages in thread]

BUG #19430: Autovacuums stopped working possible due to problem with vacuuming shared catalog pg_authid
  2026-03-12 09:24 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19430: Autovacuums stopped working possible due to problem with vacuuming shared catalog pg_authid
  2026-03-12 19:47 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [2+ messages in thread]

BUG #19431: limitation of the data type jsonb equals 8Kb
  2026-03-12 12:11 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19431: limitation of the data type jsonb equals 8Kb
  2026-03-12 14:09 UTC  Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #19431: limitation of the data type jsonb equals 8Kb
  2026-03-12 15:55 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19431: limitation of the data type jsonb equals 8Kb
  2026-03-12 17:23 UTC  Andrew Dunstan <andrew@dunslane.net>
  [4+ messages in thread]

BUG #19428: Lazy evaluation of type checking in CASE in SQL functions including subqueries no longer works in 18
  2026-03-11 16:50 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19428: Lazy evaluation of type checking in CASE in SQL functions including subqueries no longer works in 18
  2026-03-11 17:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19428: Lazy evaluation of type checking in CASE in SQL functions including subqueries no longer works in 18
  2026-03-12 09:34 UTC  Damian Lukowski <pgsql-bugs@arcsin.de>
` Re: BUG #19428: Lazy evaluation of type checking in CASE in SQL functions including subqueries no longer works in 18
  2026-03-12 12:40 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19428: Lazy evaluation of type checking in CASE in SQL functions including subqueries no longer works in 18
  2026-03-12 12:49 UTC  Damian Lukowski <pgsql-bugs@arcsin.de>
` Re: BUG #19428: Lazy evaluation of type checking in CASE in SQL functions including subqueries no longer works in 18
  2026-03-12 13:29 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19428: Lazy evaluation of type checking in CASE in SQL functions including subqueries no longer works in 18
  2026-03-12 15:46 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19428: Lazy evaluation of type checking in CASE in SQL functions including subqueries no longer works in 18
  2026-03-12 16:03 UTC  Damian Lukowski <pgsql-bugs@arcsin.de>
  [8+ messages in thread]

BUG #19427: TOAST Snapshot Assertion Failure
  2026-03-11 09:21 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19427: TOAST Snapshot Assertion Failure
  2026-03-11 16:00 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
  [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