pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #19804: "variable not found in subplan target list", DISTINCT agg over Gather`
  2026-10-28 17:20 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19804: "variable not found in subplan target list", DISTINCT agg over Gather`
  2026-10-29 15:39 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19804: "variable not found in subplan target list", DISTINCT agg over Gather`
  2026-10-29 16:17 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19804: "variable not found in subplan target list", DISTINCT agg over Gather`
  2026-10-30 08:08 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19804: "variable not found in subplan target list", DISTINCT agg over Gather`
  2026-11-09 04:41 UTC  Tender Wang <tndrwang@gmail.com>
  [5+ messages in thread]

BUG #19852: NOT IN -> anti-join conversion gives wrong results when the equality operator returns NULL for non-n
  2026-11-08 04:31 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19852: NOT IN -> anti-join conversion gives wrong results when the equality operator returns NULL for non-n
  2026-11-09 00:59 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #19852: NOT IN -> anti-join conversion gives wrong results when the equality operator returns NULL for non-n
  2026-11-09 02:36 UTC  Keyerror Smart <smartkeyerror@gmail.com>
  [3+ messages in thread]

 BUG #19788: Chinese translation uses incorrect term for “transaction” in “no transaction is in progress”
  2026-10-22 05:42 UTC  PG Bug reporting form <noreply@postgresql.org>
`  Re: BUG #19788: Chinese translation uses incorrect term for “transaction” in “no transaction is in progress”
  2026-11-08 03:06 UTC  shihao zhong <zhong950419@gmail.com>
`  Re: BUG #19788: Chinese translation uses incorrect term for “transaction” in “no transaction is in progress”
  2026-11-08 03:08 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19788: Chinese translation uses incorrect term for “transaction” in “no transaction is in progress”
  2026-11-08 15:10 UTC  Ruohang Feng <rh@vonng.com>
` Re: BUG #19788: Chinese translation uses incorrect term for “transaction” in “no transaction is in progress”
  2026-11-08 15:12 UTC  Ruohang Feng <rh@vonng.com>
  [5+ messages in thread]

BUG #19845: pg_dump extended stats break when column numbers change on restore
  2026-11-07 14:19 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19845: pg_dump extended stats break when column numbers change on restore
  2026-11-07 14:20 UTC  Atisss hh <125atishprak@gmail.com>
` Re: BUG #19845: pg_dump extended stats break when column numbers change on restore
  2026-11-08 05:30 UTC  Michael Paquier <michael@paquier.xyz>
  [3+ messages in thread]

BUG #19850: SQL/JSON .datetime() output depends on DateStyle/TimeZone but is judged IMMUTABLE - expression index
  2026-11-08 03:25 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19808: NOT NULL NO INHERIT copied by CREATE TABLE (LIKE) not enforced on partitioned table
  2026-10-29 06:20 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19808: NOT NULL NO INHERIT copied by CREATE TABLE (LIKE) not enforced on partitioned table
  2026-11-08 03:23 UTC  shihao zhong <zhong950419@gmail.com>
  [2+ messages in thread]

BUG #19806: Wrong results: HAVING pushed into WHERE for GROUP BY on composite column (nondeterministic field)
  2026-10-29 06:14 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19806: Wrong results: HAVING pushed into WHERE for GROUP BY on composite column (nondeterministic field)
  2026-11-08 03:21 UTC  shihao zhong <zhong950419@gmail.com>
  [2+ messages in thread]

 set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET
  2026-10-27 07:15 UTC  Manav Kumar <mkumar@yugabyte.com>
`  Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET
  2026-11-04 03:46 UTC  shihao zhong <zhong950419@gmail.com>
` Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET
  2026-11-04 12:13 UTC  Daniel Gustafsson <daniel@yesql.se>
`  Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET
  2026-11-04 14:47 UTC  shihao zhong <zhong950419@gmail.com>
` Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET
  2026-11-04 15:27 UTC  Daniel Gustafsson <daniel@yesql.se>
`  Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET
  2026-11-04 21:05 UTC  shihao zhong <zhong950419@gmail.com>
` Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET
  2026-11-05 09:53 UTC  Daniel Gustafsson <daniel@yesql.se>
`  Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET
  2026-11-08 02:18 UTC  shihao zhong <zhong950419@gmail.com>
  [8+ messages in thread]

BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-08-29 05:38 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-09-02 03:08 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-09-02 03:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-09-04 15:54 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-09-04 17:27 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-09-08 08:34 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-10-19 12:45 UTC  Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-10-20 06:16 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-10-20 13:20 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-10-20 16:05 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-10-20 16:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-10-21 02:39 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-10-21 04:40 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-10-29 14:42 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
  2026-11-08 01:30 UTC  shihao zhong <zhong950419@gmail.com>
  [15+ messages in thread]

BUG #19847: pg_dump loses ENFORCED on inherited CHECK under NOT ENFORCED parent
  2026-11-07 15:12 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19846: dump/restore marks inherited NOT VALID not-null constraint as local
  2026-11-07 15:10 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19844: COPY ON_ERROR set_null error context names the wrong column
  2026-11-07 14:14 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19844: COPY ON_ERROR set_null error context names the wrong column
  2026-11-07 14:16 UTC  Atisss hh <125atishprak@gmail.com>
  [2+ messages in thread]

Incompatible declarations of pg_reg_getcolor() in regcomp.c and regexec.c
  2026-11-06 20:04 UTC  Grant Jurgensen <grant@kestrel.edu>
` Re: Incompatible declarations of pg_reg_getcolor() in regcomp.c and regexec.c
  2026-11-06 20:32 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Incompatible declarations of pg_reg_getcolor() in regcomp.c and regexec.c
  2026-11-06 20:47 UTC  Grant Jurgensen <grant@kestrel.edu>
  [3+ messages in thread]

BUG #19838: pg_plan_advice: generated GATHER advice fails when supplied back
  2026-11-06 19:25 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19835: view with GROUP BY ROLLUP over duplicate columns changes results after dump/restore
  2026-11-06 17:17 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19733: Row not visible to a new snapshot after its transactional logical decoding message has been streamed
  2026-09-30 04:30 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19733: Row not visible to a new snapshot after its transactional logical decoding message has been streamed
  2026-10-07 09:14 UTC  Rahul <rahul@rhyadav.dev>
` Re: BUG #19733: Row not visible to a new snapshot after its transactional logical decoding message has been streamed
  2026-10-13 09:39 UTC  Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: BUG #19733: Row not visible to a new snapshot after its transactional logical decoding message has been streamed
  2026-11-06 15:18 UTC  Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
  [4+ messages in thread]

EXPLAIN (ANALYZE, FORMAT JSON) emits invalid output for MERGE on a partitioned table
  2026-11-06 10:39 UTC  Hironobu SUZUKI <hironobu@interdb.jp>

BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-08-03 07:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-08-03 13:16 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-11-04 09:05 UTC  Aleksander Alekseev <aleksander@tigerdata.com>
` Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-11-04 09:36 UTC  Aleksander Alekseev <aleksander@tigerdata.com>
` Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-11-04 15:58 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-11-05 08:17 UTC  Aleksander Alekseev <aleksander@tigerdata.com>
` Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-11-05 11:12 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-11-06 09:00 UTC  Aleksander Alekseev <aleksander@tigerdata.com>
` Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-11-06 09:56 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
  [9+ messages in thread]

BUG #19768: JSON_TABLE: row/text comparisons in context item or PASSING give wrong results or spurious collation
  2026-10-16 22:51 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19768: JSON_TABLE: row/text comparisons in context item or PASSING give wrong results or spurious collation
  2026-10-16 23:06 UTC  Venu K <venu2805k@gmail.com>
` Re: BUG #19768: JSON_TABLE: row/text comparisons in context item or PASSING give wrong results or spurious collation
  2026-10-23 19:14 UTC  Venu K <venu2805k@gmail.com>
` Re: BUG #19768: JSON_TABLE: row/text comparisons in context item or PASSING give wrong results or spurious collation
  2026-11-06 02:31 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19768: JSON_TABLE: row/text comparisons in context item or PASSING give wrong results or spurious collation
  2026-11-06 08:34 UTC  Amit Langote <amitlangote09@gmail.com>
  [5+ messages in thread]

[Bug] Heap use-after-free in COPY FROM error context after ON_ERROR ignore skips a row
  2026-10-28 10:12 UTC  Gowdham M <gowdham.m@zohocorp.com>
` Re: [Bug] Heap use-after-free in COPY FROM error context after ON_ERROR ignore skips a row
  2026-11-03 03:40 UTC  shihao zhong <zhong950419@gmail.com>
` Re: [Bug] Heap use-after-free in COPY FROM error context after ON_ERROR ignore skips a row
  2026-11-03 06:50 UTC  Gowdham M <gowdham.m@zohocorp.com>
` Re: [Bug] Heap use-after-free in COPY FROM error context after ON_ERROR ignore skips a row
  2026-11-05 04:18 UTC  Michael Paquier <michael@paquier.xyz>
` Re: [Bug] Heap use-after-free in COPY FROM error context after ON_ERROR ignore skips a row
  2026-11-06 00:20 UTC  Michael Paquier <michael@paquier.xyz>
  [5+ messages in thread]

BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-02-26 09:57 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-02-26 14:20 UTC  Vik Fearing <vik@postgresfriends.org>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-02-27 14:44 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-03-02 05:09 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-03-02 05:45 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-03-02 06:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-03-03 01:03 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-03-03 02:41 UTC  jian he <jian.universality@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-03-03 07:16 UTC  Lukas Eder <lukas.eder@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-03-03 14:32 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-03-04 06:35 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-16 06:04 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-20 08:29 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-20 09:05 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-21 00:57 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-21 01:12 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-21 02:30 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-21 03:20 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-21 03:57 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-21 05:45 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-23 00:55 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-23 06:51 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-24 12:04 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-24 19:58 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-04-30 22:04 UTC  Melanie Plageman <melanieplageman@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-05-01 00:26 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-05-01 01:23 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-05-07 14:44 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-05-08 08:35 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: [***DKIM violation***] Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-10-16 11:54 UTC  Staroverov Ilja <i.staroverov@ftdata.ru>
` Re: [***DKIM violation***] Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-10-29 03:11 UTC  jian he <jian.universality@gmail.com>
` Re: [***DKIM violation***] Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-11-05 13:15 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: [***DKIM violation***] Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
  2026-11-06 00:08 UTC  Amit Langote <amitlangote09@gmail.com>
  [33+ messages in thread]

BUG #19832: convert() between BIG5 and EUC_TW returns different characters than PostgreSQL's own UTF-8 mappings
  2026-11-05 09:32 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19775: Incremental backup without data checksums restores a stale visibility map page after VACUUM truncati
  2026-10-20 03:40 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19775: Incremental backup without data checksums restores a stale visibility map page after VACUUM truncati
  2026-10-23 02:01 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19775: Incremental backup without data checksums restores a stale visibility map page after VACUUM truncati
  2026-10-23 03:01 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19775: Incremental backup without data checksums restores a stale visibility map page after VACUUM truncati
  2026-11-04 13:55 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19775: Incremental backup without data checksums restores a stale visibility map page after VACUUM truncati
  2026-11-04 14:33 UTC  shihao zhong <zhong950419@gmail.com>
` Re: BUG #19775: Incremental backup without data checksums restores a stale visibility map page after VACUUM truncati
  2026-11-05 09:10 UTC  Fujii Masao <masao.fujii@gmail.com>
  [6+ messages in thread]

BUG #19831: convert() between single-byte Cyrillic encodings returns wrong characters (KOI8R<->WIN866, WIN866->W
  2026-11-05 09:00 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-08-15 03:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-08-16 14:29 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-08-18 02:06 UTC  zengman <zengman@halodbtech.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-08-18 08:56 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-04 10:38 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-23 20:12 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-24 17:06 UTC  Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-24 17:38 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-26 16:28 UTC  jian he <jian.universality@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-26 18:14 UTC  Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-09-28 04:03 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-11-04 10:05 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-11-04 16:28 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
  2026-11-05 04:02 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
  [14+ 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