pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
PostgreSQL 17 Service Running but Not Listening on Network Port on Windows
  2025-06-18 15:38 UTC  José António Gomes <jose.antonio.luanda@gmail.com>
` Re: PostgreSQL 17 Service Running but Not Listening on Network Port on Windows
  2025-06-18 20:46 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: PostgreSQL 17 Service Running but Not Listening on Network Port on Windows
  2025-06-18 20:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-06 06:39 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-07 16:49 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-08 02:39 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-08 10:25 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-09 10:07 UTC  Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-10 05:45 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-10 10:02 UTC  Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-10 11:14 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-10 22:39 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-10 22:57 UTC  Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-11 00:03 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-11 09:04 UTC  Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-11 23:46 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-12 23:50 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
  2025-06-18 06:33 UTC  Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
  [15+ messages in thread]

BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9
  2025-05-30 19:43 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9
  2025-05-30 20:02 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9
  2025-06-17 17:41 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9
  2025-06-17 20:10 UTC  Laurence Parry <greenreaper@hotmail.com>
  [4+ messages in thread]

BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672"
  2025-05-28 03:30 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672"
  2025-05-28 17:15 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: [E] Re: BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672"
  2025-05-28 19:13 UTC  John Hutchins <John.Hutchins@WICOURTS.GOV>
` Re: [E] Re: BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672"
  2025-05-29 03:32 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: [E] Re: BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672"
  2025-06-17 17:42 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
  [5+ messages in thread]

Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build
  2025-06-11 18:10 UTC  Soumyadeep Chakraborty <soumyadeep2007@gmail.com>
` Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build
  2025-06-11 21:42 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build
  2025-06-12 06:57 UTC  John Naylor <johncnaylorls@gmail.com>
` Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build
  2025-06-12 17:30 UTC  Soumyadeep Chakraborty <soumyadeep2007@gmail.com>
` Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build
  2025-06-13 14:03 UTC  John Naylor <johncnaylorls@gmail.com>
` Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build
  2025-06-15 01:23 UTC  Andy Fan <zhihuifan1213@163.com>
` Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build
  2025-06-16 02:32 UTC  John Naylor <johncnaylorls@gmail.com>
  [7+ messages in thread]

BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-07 16:08 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 00:27 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 01:40 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 02:07 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 02:57 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 02:59 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 03:02 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 03:04 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 03:08 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 03:11 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 03:16 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 03:26 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-08 03:34 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-09 23:35 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-14 14:27 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-14 15:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-14 15:52 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-14 16:12 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-14 21:35 UTC  Lowell Hought <lowell.hought@gmail.com>
` Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  2025-06-14 22:26 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [20+ messages in thread]

BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows
  2025-06-13 13:21 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows
  2025-06-13 13:46 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows
  2025-06-13 14:51 UTC  Seva Zaslavsky <szaslavsky@mpcapitallp.com>
` Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows
  2025-06-13 14:58 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows
  2025-06-13 19:50 UTC  Seva Zaslavsky <szaslavsky@mpcapitallp.com>
` Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows
  2025-06-13 20:04 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [6+ messages in thread]

BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-02 06:34 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-02 08:13 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-02 17:00 UTC  Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-02 23:31 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-03 09:56 UTC  Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-04 00:12 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-11 03:58 UTC  Никита Калинин <n.kalinin@postgrespro.ru>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-11 14:11 UTC  Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-11 22:34 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-12 07:38 UTC  Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-12 08:03 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-12 13:04 UTC  Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
` Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set
  2025-06-13 01:19 UTC  Michael Paquier <michael@paquier.xyz>
  [13+ messages in thread]

BUG #18952: pg_restore --help and document have strange description: Dump something
  2025-06-10 07:35 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18952: pg_restore --help and document have strange description: Dump something
  2025-06-11 01:04 UTC  Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #18952: pg_restore --help and document have strange description: Dump something
  2025-06-11 02:38 UTC  TAKATSUKA Haruka <harukat@sraoss.co.jp>
` Re: BUG #18952: pg_restore --help and document have strange description: Dump something
  2025-06-12 12:20 UTC  Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #18952: pg_restore --help and document have strange description: Dump something
  2025-06-12 12:28 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18952: pg_restore --help and document have strange description: Dump something
  2025-06-12 14:27 UTC  Fujii Masao <masao.fujii@oss.nttdata.com>
  [6+ messages in thread]

BUG #18956: Observing an issue in regexp_count()
  2025-06-12 08:03 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18956: Observing an issue in regexp_count()
  2025-06-12 12:10 UTC  hubert depesz lubaczewski <depesz@depesz.com>
` Re: BUG #18956: Observing an issue in regexp_count()
  2025-06-12 13:54 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18956: Observing an issue in regexp_count()
  2025-06-12 14:05 UTC  hubert depesz lubaczewski <depesz@depesz.com>
  [4+ messages in thread]

BUG #18955: pg_ctl output not being logged in stderr log on Windows if started with "net start"
  2025-06-11 12:34 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #18954: Error "could not reserve shared memory region ... error code 487" on Windows
  2025-06-11 11:22 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #18804: LISTEN on channel fails with "could not access status of transaction"
  2025-02-11 16:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction"
  2025-06-10 10:02 UTC  Andrei Varashen <voroshen.av@gmail.com>
` Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction"
  2025-06-10 14:44 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [3+ messages in thread]

BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq
  2025-04-29 16:35 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq
  2025-04-29 18:06 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq
  2025-04-29 18:48 UTC  Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq
  2025-06-07 05:01 UTC  BATBAATAR Dorjpalam <htgn.dbat.95@gmail.com>
` Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq
  2025-06-07 07:20 UTC  BATBAATAR Dorjpalam <htgn.dbat.95@gmail.com>
` Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq
  2025-06-09 14:26 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq
  2025-06-09 17:02 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq
  2025-06-10 00:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [8+ messages in thread]

tlsv1 alert unknown ca error on cert authentication
  2025-06-08 12:21 UTC  Andrus <kobruleht2@hot.ee>
` Re: tlsv1 alert unknown ca error on cert authentication
  2025-06-08 16:14 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: tlsv1 alert unknown ca error on cert authentication
  2025-06-09 07:34 UTC  Andrus <kobruleht2@hot.ee>
` Re: tlsv1 alert unknown ca error on cert authentication
  2025-06-09 15:39 UTC  Jacob Champion <jacob.champion@enterprisedb.com>
` Re: tlsv1 alert unknown ca error on cert authentication
  2025-06-09 20:40 UTC  Andrus <kobruleht2@hot.ee>
  [5+ messages in thread]

BUG #18951: Precision loss in inner join while using SUM aggregate function
  2025-06-08 14:38 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18951: Precision loss in inner join while using SUM aggregate function
  2025-06-08 15:44 UTC  Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #18951: Precision loss in inner join while using SUM aggregate function
  2025-06-08 15:50 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #18948: Equivalent MAX() result in view and inline query yields inconsistent row count
  2025-06-07 02:44 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18948: Equivalent MAX() result in view and inline query yields inconsistent row count
  2025-06-07 16:09 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

Function Error Response Is Not Clear
  2025-06-06 02:50 UTC  Luke Muther <lmutes8@gmail.com>
` Re: Function Error Response Is Not Clear
  2025-06-07 16:05 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

 BUG #18949: 分区表创建主键或者唯一约束需要有分区键
  2025-06-07 09:29 UTC  PG Bug reporting form <noreply@postgresql.org>
`  Re: BUG #18949: 分区表创建主键或者唯一约束需要有分区键
  2025-06-07 15:55 UTC  Dilip Kumar <dilipbalaut@gmail.com>
  [2+ messages in thread]

BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw
  2025-05-29 16:59 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw
  2025-06-04 11:39 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw
  2025-06-04 16:28 UTC  Joseph Ayers <joseph.ayers@crunchydata.com>
` Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw
  2025-06-04 16:32 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw
  2025-06-05 23:08 UTC  Joseph Ayers <joseph.ayers@crunchydata.com>
` Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw
  2025-06-06 12:17 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw
  2025-06-07 10:11 UTC  Thomas Munro <thomas.munro@gmail.com>
  [7+ messages in thread]

BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-05-08 19:55 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-02 14:05 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-02 17:16 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-02 19:56 UTC  Rahila Syed <rahilasyed90@gmail.com>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-02 20:53 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-02 22:56 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-03 05:48 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-03 12:31 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-04 00:44 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-04 09:42 UTC  Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-04 11:31 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
  2025-06-04 11:32 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
  [12+ messages in thread]

BUG #18946: Installation Setup File
  2025-06-03 09:23 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18946: Installation Setup File
  2025-06-03 13:30 UTC  Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
  [2+ messages in thread]

BUG #18945: Standby synchronization problem
  2025-06-02 12:18 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18945: Standby synchronization problem
  2025-06-02 13:12 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18945: Standby synchronization problem
  2025-06-03 06:13 UTC  Michael Paquier <michael@paquier.xyz>
  [3+ messages in thread]

function 'IS JSON ARRAY' not identified
  2025-06-02 14:41 UTC  Badia, Antonio <antonio.badia@louisville.edu>
` Re: function 'IS JSON ARRAY' not identified
  2025-06-02 15:19 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: function 'IS JSON ARRAY' not identified
  2025-06-02 15:26 UTC  Badia, Antonio <antonio.badia@louisville.edu>
  [3+ messages in thread]

BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always
  2025-05-12 09:51 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always
  2025-05-13 14:22 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always
  2025-05-14 19:35 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always
  2025-05-31 23:46 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ 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