agora inbox for pgsql-bugs@postgresql.org
help / color / mirror / Atom feedBUG #19650: to_date()/to_timestamp() silently truncate 4+-digit day-of-year input to the first three digits
2026-09-03 06:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19650: to_date()/to_timestamp() silently truncate 4+-digit day-of-year input to the first three digits
2026-09-03 15:29 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19650: to_date()/to_timestamp() silently truncate 4+-digit day-of-year input to the first three digits
2026-09-09 04:31 UTC Clemenza Zhang <zxlmgsps2@gmail.com>
[3+ messages in thread]
pg_restore_attribute_stats accepts an unsorted range-length histogram
2026-09-08 09:56 UTC =?utf-8?B?4pmCz4DiiYwyNjIxOA==?= <1991230470@qq.com>
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>
[6+ messages in thread]
BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-04 06:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-04 14:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-04 14:59 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-04 15:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-04 23:09 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-05 13:26 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-06 17:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-07 02:00 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-07 03:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-07 08:27 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-07 15:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
2026-09-08 01:29 UTC Richard Guo <guofenglinux@gmail.com>
[12+ messages in thread]
BUG #19678: int16 Overflow in tsquery Phrase Distance After Stopword Removal
2026-09-07 14:21 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19677: Silent int64→int32 Truncation in timestamp_izone() Produces Wrong Timestamps
2026-09-07 14:19 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19673: inetmi_int8 Signed Integer Overflow Returns Wrong IPv6 Address
2026-09-07 14:12 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19672: int8shl/int8shr Undefined Behavior on Out-of-Range Shift Amounts
2026-09-07 14:10 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19670: Silent Integer Overflow in time_pl_interval() Returns Wrong Time Value
2026-09-07 14:06 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-03 06:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-03 21:17 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-04 15:12 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-04 16:10 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-05 07:52 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-05 10:45 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-05 16:23 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-05 16:48 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-06 13:09 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[9+ messages in thread]
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 =?ISO-8859-1?B?emVuZ21hbg==?= <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>
[5+ messages in thread]
BUG #19654: JSON_EXISTS returns ON ERROR value for SQL NULL after a prior error
2026-09-04 09:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19654: JSON_EXISTS returns ON ERROR value for SQL NULL after a prior error
2026-09-04 10:12 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
BUG #19628: Uninterruptible vacuum during hash index processing
2026-08-18 12:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-08-22 14:54 UTC mostafa nabil <mostafa.nabil.nafie@gmail.com>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-09-03 06:48 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-09-04 09:47 UTC mostafa nabil <mostafa.nabil.nafie@gmail.com>
[4+ messages in thread]
BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-18 03:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-18 13:29 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-19 02:28 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-19 07:02 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-25 19:23 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-25 20:02 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-09-04 03:11 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-09-04 06:38 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-09-04 08:13 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[9+ messages in thread]
BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-08-30 17:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-02 18:51 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-02 20:43 UTC Edwin Polkerman <edwin.polkerman@splendiddata.com>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-02 21:19 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-03 11:55 UTC Edwin Polkerman <edwin.polkerman@splendiddata.com>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-03 16:49 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-03 19:35 UTC Edwin Polkerman <edwin.polkerman@splendiddata.com>
[7+ messages in thread]
BUG #19652: to_number() silently truncates over-length integers
2026-09-03 06:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19652: to_number() silently truncates over-length integers
2026-09-03 18:36 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
BUG #19651: to_date()/to_timestamp() silently accept out-of-range values for SSSSS, RM, IW and ID format fields
2026-09-03 06:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19651: to_date()/to_timestamp() silently accept out-of-range values for SSSSS, RM, IW and ID format fields
2026-09-03 15:36 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-03-29 10:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-08-27 08:16 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-08-27 08:49 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-09-02 11:01 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-09-02 11:44 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-09-03 03:20 UTC Fujii Masao <masao.fujii@gmail.com>
[6+ messages in thread]
BUG #19645: Partition key opclass bypasses nondeterministic collation check, wrong results
2026-08-29 05:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19645: Partition key opclass bypasses nondeterministic collation check, wrong results
2026-09-02 06:28 UTC Zexin Li <lizi.openmind@gmail.com>
[2+ messages in thread]
BUG #19487: Error while executing SQL query involving XML parsing
2026-05-19 09:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-28 08:53 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-28 19:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-28 19:55 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-29 10:54 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-29 21:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-30 03:08 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-30 18:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-30 18:35 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-09-01 16:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-09-01 16:37 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[11+ messages in thread]
to_char() on integer with V format silently wraps on overflow
2026-08-13 12:01 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: to_char() on integer with V format silently wraps on overflow
2026-08-27 08:57 UTC Miłosz Bieniek <bieniek.milosz@proton.me>
` Re: to_char() on integer with V format silently wraps on overflow
2026-08-27 10:30 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: to_char() on integer with V format silently wraps on overflow
2026-08-27 21:26 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: to_char() on integer with V format silently wraps on overflow
2026-09-01 02:46 UTC Fujii Masao <masao.fujii@gmail.com>
[5+ messages in thread]
BUG #19648: Docs on DISTINCT ON do not describe how expressions are matched to ORDER BY
2026-08-31 23:10 UTC PG Bug reporting form <noreply@postgresql.org>
repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-19 11:03 UTC Jochen Bandhauer <jb@jbitc.de>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-19 16:16 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-25 19:57 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-25 21:00 UTC Jochen Bandhauer <jb@jbitc.de>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-26 00:44 UTC Fujii Masao <masao.fujii@gmail.com>
` Fwd: Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-26 07:18 UTC Jochen Bandhauer <jb@jbitc.de>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-26 12:56 UTC Jochen Bandhauer <jb@jbitc.de>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-31 11:20 UTC Jochen Bandhauer <jb@jbitc.de>
[8+ messages in thread]
BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 01:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 07:29 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 17:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 17:42 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 20:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 20:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-24 11:20 UTC Ewan Young <kdbase.hack@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 00:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 04:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 04:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 04:30 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 04:37 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 04:43 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 11:43 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
[15+ messages in thread]
BUG #19646: Unique index with explicit COLLATE bypasses nondeterministic collation rule
2026-08-29 05:39 UTC PG Bug reporting form <noreply@postgresql.org>
[next (older)]
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox