pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
8+ messages / 4 participants
[nested] [flat]

Commits from this thread:
  2026-11-11 1d657c6e01 a9faa96b66 19a5f3e405 21b7a3fd68 672081106e 578f74fd8b  Fix uninitialized cache use in gtsvector_picksplit()
* BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
@ 2026-10-21 18:00 PG Bug reporting form <noreply@postgresql.org>
  2026-11-04 05:42 ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries shihao zhong <zhong950419@gmail.com>
  0 siblings, 1 reply; 8+ messages in thread

From: PG Bug reporting form @ 2026-10-21 18:00 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: exclusion@gmail.com

The following bug has been logged on the website:

Bug reference:      19780
Logged by:          Alexander Lakhin
Email address:      exclusion@gmail.com
PostgreSQL version: 19rc1
Operating system:   Ubuntu 24.04
Description:        

The following script:
CREATE TABLE t (i tsvector, j tsvector);
CREATE INDEX t_idx ON t USING gist (i tsvector_ops (siglen = '1800'), j
tsvector_ops);
INSERT INTO t SELECT (SELECT string_agg(g::text, ' ')::tsvector FROM
generate_series(1, 200) g), 'x'::tsvector FROM generate_series(1, 4);

INSERT INTO t SELECT (SELECT string_agg(g::text, ' ')::tsvector FROM
generate_series(1, 200) g) || 'a', 'x'::tsvector;

being executed under Valgrind, triggers:
==00:00:00:57.066 1678143== Conditional jump or move depends on
uninitialised value(s)
==00:00:00:57.066 1678143==    at 0x48CBC35: gtsvector_picksplit
(tsgistidx.c:685)
==00:00:00:57.066 1678143==    by 0x493208E: FunctionCall2Coll (fmgr.c:1163)
==00:00:00:57.066 1678143==    by 0x41409A3: gistUserPicksplit
(gistsplit.c:433)
==00:00:00:57.066 1678143==    by 0x414127B: gistSplitByKey
(gistsplit.c:697)
==00:00:00:57.066 1678143==    by 0x4141504: gistSplitByKey
(gistsplit.c:747)
==00:00:00:57.066 1678143==    by 0x4134199: gistSplit (gist.c:1483)
==00:00:00:57.066 1678143==    by 0x4131D58: gistplacetopage (gist.c:316)
==00:00:00:57.066 1678143==    by 0x4133D6D: gistinserttuples (gist.c:1310)
==00:00:00:57.066 1678143==    by 0x4133CC7: gistinserttuple (gist.c:1263)
==00:00:00:57.066 1678143==    by 0x413310D: gistdoinsert (gist.c:892)
==00:00:00:57.067 1678143==    by 0x41319E7: gistinsert (gist.c:191)
==00:00:00:57.067 1678143==    by 0x4184D62: index_insert (indexam.c:231)
==00:00:00:57.067 1678143==

Reproduced on REL_14_STABLE .. master.








^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
  2026-10-21 18:00 BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries PG Bug reporting form <noreply@postgresql.org>
@ 2026-11-04 05:42 ` shihao zhong <zhong950419@gmail.com>
  2026-11-04 15:48   ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Ayush Tiwari <ayushtiwari.slg01@gmail.com>
  2026-11-06 07:52   ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
  0 siblings, 2 replies; 8+ messages in thread

From: shihao zhong @ 2026-11-04 05:42 UTC (permalink / raw)
  To: exclusion@gmail.com; pgsql-bugs@lists.postgresql.org

Hi Alexander,

Thanks for the report. With only two entries, the cache of the second
one is used before it is filled.

Your two column case is harmless. With one column, the index can miss
rows until REINDEX.

The attached patch fills the cache earlier and adds a test.

Thanks,
Shihao

Attachments:

v1-0001-Fix-gtsvector_picksplit-with-only-two-entries.patch (application/octet-stream, 3.5K) download From f7b89485dc12b71384378ea1170c1e2b0b97ae70 Mon Sep 17 00:00:00 2001 From: shihao zhong <zhong950419@gmail.com> Date: Tue, 3 Nov 2026 22:46:12 -0500 Subject: [PATCH] Fix gtsvector_picksplit() with only two entries Fill the cache for the last entry before forming the initial unions. Existing single-column indexes may need a REINDEX. Reported-by: Alexander Lakhin <exclusion@gmail.com> Discussion: https://postgr.es/m/19780-93fb5c0e4ec2af18@postgresql.org Backpatch-through: 14 --- src/backend/utils/adt/tsgistidx.c | 6 ++++-- src/test/regress/expected/tsearch.out | 16 ++++++++++++++++ src/test/regress/sql/tsearch.sql | 12 ++++++++++++ 3 files changed, 32 insertions(+), 2 deletions(-) diff --git a/src/backend/utils/adt/tsgistidx.c b/src/backend/utils/adt/tsgistidx.c index 1befe4fbedf..f384cf205d6 100644 --- a/src/backend/utils/adt/tsgistidx.c +++ b/src/backend/utils/adt/tsgistidx.c @@ -678,6 +678,10 @@ gtsvector_picksplit(PG_FUNCTION_ARGS) seed_2 = 2; } + /* seed_2 can be the last entry, so fill its cache first */ + maxoff = OffsetNumberNext(maxoff); + fillcache(&cache[maxoff], GETENTRY(entryvec, maxoff), siglen); + /* form initial .. */ datum_l = gtsvector_alloc(SIGNKEY | (cache[seed_1].allistrue ? ALLISTRUE : 0), siglen, cache[seed_1].sign); @@ -685,8 +689,6 @@ gtsvector_picksplit(PG_FUNCTION_ARGS) siglen, cache[seed_2].sign); union_l = GETSIGN(datum_l); union_r = GETSIGN(datum_r); - maxoff = OffsetNumberNext(maxoff); - fillcache(&cache[maxoff], GETENTRY(entryvec, maxoff), siglen); /* sort before ... */ costvector = palloc_array(SPLITCOST, maxoff); for (j = FirstOffsetNumber; j <= maxoff; j = OffsetNumberNext(j)) diff --git a/src/test/regress/expected/tsearch.out b/src/test/regress/expected/tsearch.out index 5b7c2123f37..22effde4efa 100644 --- a/src/test/regress/expected/tsearch.out +++ b/src/test/regress/expected/tsearch.out @@ -870,6 +870,22 @@ RESET enable_seqscan; RESET enable_indexscan; RESET enable_bitmapscan; DROP INDEX wowidx; +-- Two index tuples that don't fit on one page +CREATE TABLE test_tsvector_wide (a tsvector, b bytea); +CREATE INDEX ON test_tsvector_wide USING gist (a) INCLUDE (b); +INSERT INTO test_tsvector_wide + SELECT 'foo', decode(string_agg(md5(g::text), ''), 'hex') + FROM generate_series(1, 300) g; +INSERT INTO test_tsvector_wide SELECT 'bar', b FROM test_tsvector_wide; +SET enable_seqscan = off; +SELECT count(*) FROM test_tsvector_wide WHERE a @@ 'bar'; + count +------- + 1 +(1 row) + +RESET enable_seqscan; +DROP TABLE test_tsvector_wide; ALTER TABLE test_tsvector SET (parallel_workers = 2); CREATE INDEX wowidx ON test_tsvector USING gin (a); SET enable_seqscan=OFF; diff --git a/src/test/regress/sql/tsearch.sql b/src/test/regress/sql/tsearch.sql index 8b3d700f57c..cea3b1fca02 100644 --- a/src/test/regress/sql/tsearch.sql +++ b/src/test/regress/sql/tsearch.sql @@ -222,6 +222,18 @@ RESET enable_bitmapscan; DROP INDEX wowidx; +-- Two index tuples that don't fit on one page +CREATE TABLE test_tsvector_wide (a tsvector, b bytea); +CREATE INDEX ON test_tsvector_wide USING gist (a) INCLUDE (b); +INSERT INTO test_tsvector_wide + SELECT 'foo', decode(string_agg(md5(g::text), ''), 'hex') + FROM generate_series(1, 300) g; +INSERT INTO test_tsvector_wide SELECT 'bar', b FROM test_tsvector_wide; +SET enable_seqscan = off; +SELECT count(*) FROM test_tsvector_wide WHERE a @@ 'bar'; +RESET enable_seqscan; +DROP TABLE test_tsvector_wide; + ALTER TABLE test_tsvector SET (parallel_workers = 2); CREATE INDEX wowidx ON test_tsvector USING gin (a); -- 2.37.1 (Apple Git-137.1)
^ permalink raw reply [nested|flat] 8+ messages in thread

* Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
  2026-10-21 18:00 BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries PG Bug reporting form <noreply@postgresql.org>
  2026-11-04 05:42 ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries shihao zhong <zhong950419@gmail.com>
@ 2026-11-04 15:48   ` Ayush Tiwari <ayushtiwari.slg01@gmail.com>
  1 sibling, 0 replies; 8+ messages in thread

From: Ayush Tiwari @ 2026-11-04 15:48 UTC (permalink / raw)
  To: shihao zhong <zhong950419@gmail.com>; +Cc: exclusion@gmail.com; pgsql-bugs@lists.postgresql.org

Hi,

On Wed, 4 Nov 2026 at 11:13, shihao zhong <zhong950419@gmail.com> wrote:
>
> Thanks for the report. With only two entries, the cache of the second
> one is used before it is filled.

+1

> Your two column case is harmless. With one column, the index can miss
> rows until REINDEX.
>
> The attached patch fills the cache earlier and adds a test.

Thanks for the patch, it looks good to me.

Regards,
Ayush






^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
  2026-10-21 18:00 BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries PG Bug reporting form <noreply@postgresql.org>
  2026-11-04 05:42 ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries shihao zhong <zhong950419@gmail.com>
@ 2026-11-06 07:52   ` Michael Paquier <michael@paquier.xyz>
  2026-11-06 08:16     ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
  1 sibling, 1 reply; 8+ messages in thread

From: Michael Paquier @ 2026-11-06 07:52 UTC (permalink / raw)
  To: shihao zhong <zhong950419@gmail.com>; +Cc: exclusion@gmail.com; pgsql-bugs@lists.postgresql.org

On Wed, Nov 04, 2026 at 12:42:55AM -0500, shihao zhong wrote:
> Thanks for the report. With only two entries, the cache of the second
> one is used before it is filled.
> 
> Your two column case is harmless. With one column, the index can miss
> rows until REINDEX.
> 
> The attached patch fills the cache earlier and adds a test.

So the problem is this one, where we could try to read the cached data
for seed_2 but it's just not initialized yet:
datum_r = gtsvector_alloc(SIGNKEY | (cache[seed_2].allistrue ?
    ALLISTRUE : 0), siglen, cache[seed_2].sign);                                                                                                                   

Calling fillcache() earlier so as datum_r and datum_l are built from
correct values is enough.  Your change makes sense.
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
  2026-10-21 18:00 BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries PG Bug reporting form <noreply@postgresql.org>
  2026-11-04 05:42 ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries shihao zhong <zhong950419@gmail.com>
  2026-11-06 07:52   ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
@ 2026-11-06 08:16     ` Michael Paquier <michael@paquier.xyz>
  2026-11-08 00:02       ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries shihao zhong <zhong950419@gmail.com>
  0 siblings, 1 reply; 8+ messages in thread

From: Michael Paquier @ 2026-11-06 08:16 UTC (permalink / raw)
  To: shihao zhong <zhong950419@gmail.com>; +Cc: exclusion@gmail.com; pgsql-bugs@lists.postgresql.org

On Fri, Nov 06, 2026 at 04:52:21PM +0900, Michael Paquier wrote:
> So the problem is this one, where we could try to read the cached data
> for seed_2 but it's just not initialized yet:
> datum_r = gtsvector_alloc(SIGNKEY | (cache[seed_2].allistrue ?
>     ALLISTRUE : 0), siglen, cache[seed_2].sign);
> 
> Calling fillcache() earlier so as datum_r and datum_l are built from
> correct values is enough.  Your change makes sense.

+INSERT INTO test_tsvector_wide
+  SELECT 'foo', decode(string_agg(md5(g::text), ''), 'hex')
+  FROM generate_series(1, 300) g;

By the way, this test is going to piss buildfarm members that have
FIPS enabled, where md5() calls fail.  Could it be possible to write a
test that's more portable across the board?  There is a v19 RC2 in
sight, and it's already late in the week here so this will have to
wait until the tag of the next version is pushed around next
Wednesday.  It's an old issue, so a few more days will not matter.

There is a fipshash() in test_setup.sql, written for portability, but
perhaps we can make the test much faster by using the same tricks as
test_decoding's toast.sql in terms of generation of long values?
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
  2026-10-21 18:00 BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries PG Bug reporting form <noreply@postgresql.org>
  2026-11-04 05:42 ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries shihao zhong <zhong950419@gmail.com>
  2026-11-06 07:52   ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
  2026-11-06 08:16     ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
@ 2026-11-08 00:02       ` shihao zhong <zhong950419@gmail.com>
  2026-11-08 22:25         ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
  0 siblings, 1 reply; 8+ messages in thread

From: shihao zhong @ 2026-11-08 00:02 UTC (permalink / raw)
  To: Michael Paquier <michael@paquier.xyz>; +Cc: exclusion@gmail.com; pgsql-bugs@lists.postgresql.org

> By the way, this test is going to piss buildfarm members that have
> FIPS enabled, where md5() calls fail.

aha. I am not aware of that.

v2 uses repeat() and sets the column to STORAGE
EXTERNAL so it stays uncompressed, like toast.sql does.

Thanks,
Shihao

Attachments:

v2-0001-Fix-gtsvector_picksplit-with-only-two-entries.patch (application/octet-stream, 3.6K) download From 6d22709412de0844db2e7a7bb697d13428c6508e Mon Sep 17 00:00:00 2001 From: shihao zhong <zhong950419@gmail.com> Date: Tue, 3 Nov 2026 22:46:12 -0500 Subject: [PATCH] Fix gtsvector_picksplit() with only two entries Fill the cache for the last entry before forming the initial unions. Existing single-column indexes may need a REINDEX. Reported-by: Alexander Lakhin <exclusion@gmail.com> Discussion: https://postgr.es/m/19780-93fb5c0e4ec2af18@postgresql.org Backpatch-through: 14 --- src/backend/utils/adt/tsgistidx.c | 6 ++++-- src/test/regress/expected/tsearch.out | 15 +++++++++++++++ src/test/regress/sql/tsearch.sql | 11 +++++++++++ 3 files changed, 30 insertions(+), 2 deletions(-) diff --git a/src/backend/utils/adt/tsgistidx.c b/src/backend/utils/adt/tsgistidx.c index 1befe4fbedf..f384cf205d6 100644 --- a/src/backend/utils/adt/tsgistidx.c +++ b/src/backend/utils/adt/tsgistidx.c @@ -678,6 +678,10 @@ gtsvector_picksplit(PG_FUNCTION_ARGS) seed_2 = 2; } + /* seed_2 can be the last entry, so fill its cache first */ + maxoff = OffsetNumberNext(maxoff); + fillcache(&cache[maxoff], GETENTRY(entryvec, maxoff), siglen); + /* form initial .. */ datum_l = gtsvector_alloc(SIGNKEY | (cache[seed_1].allistrue ? ALLISTRUE : 0), siglen, cache[seed_1].sign); @@ -685,8 +689,6 @@ gtsvector_picksplit(PG_FUNCTION_ARGS) siglen, cache[seed_2].sign); union_l = GETSIGN(datum_l); union_r = GETSIGN(datum_r); - maxoff = OffsetNumberNext(maxoff); - fillcache(&cache[maxoff], GETENTRY(entryvec, maxoff), siglen); /* sort before ... */ costvector = palloc_array(SPLITCOST, maxoff); for (j = FirstOffsetNumber; j <= maxoff; j = OffsetNumberNext(j)) diff --git a/src/test/regress/expected/tsearch.out b/src/test/regress/expected/tsearch.out index 5b7c2123f37..357442866a5 100644 --- a/src/test/regress/expected/tsearch.out +++ b/src/test/regress/expected/tsearch.out @@ -870,6 +870,21 @@ RESET enable_seqscan; RESET enable_indexscan; RESET enable_bitmapscan; DROP INDEX wowidx; +-- Two index tuples that don't fit on one page +CREATE TABLE test_tsvector_wide (a tsvector, b text); +ALTER TABLE test_tsvector_wide ALTER COLUMN b SET STORAGE EXTERNAL; +CREATE INDEX ON test_tsvector_wide USING gist (a) INCLUDE (b); +INSERT INTO test_tsvector_wide VALUES ('foo', repeat('x', 5000)); +INSERT INTO test_tsvector_wide SELECT 'bar', b FROM test_tsvector_wide; +SET enable_seqscan = off; +SELECT count(*) FROM test_tsvector_wide WHERE a @@ 'bar'; + count +------- + 1 +(1 row) + +RESET enable_seqscan; +DROP TABLE test_tsvector_wide; ALTER TABLE test_tsvector SET (parallel_workers = 2); CREATE INDEX wowidx ON test_tsvector USING gin (a); SET enable_seqscan=OFF; diff --git a/src/test/regress/sql/tsearch.sql b/src/test/regress/sql/tsearch.sql index 8b3d700f57c..b81722b47eb 100644 --- a/src/test/regress/sql/tsearch.sql +++ b/src/test/regress/sql/tsearch.sql @@ -222,6 +222,17 @@ RESET enable_bitmapscan; DROP INDEX wowidx; +-- Two index tuples that don't fit on one page +CREATE TABLE test_tsvector_wide (a tsvector, b text); +ALTER TABLE test_tsvector_wide ALTER COLUMN b SET STORAGE EXTERNAL; +CREATE INDEX ON test_tsvector_wide USING gist (a) INCLUDE (b); +INSERT INTO test_tsvector_wide VALUES ('foo', repeat('x', 5000)); +INSERT INTO test_tsvector_wide SELECT 'bar', b FROM test_tsvector_wide; +SET enable_seqscan = off; +SELECT count(*) FROM test_tsvector_wide WHERE a @@ 'bar'; +RESET enable_seqscan; +DROP TABLE test_tsvector_wide; + ALTER TABLE test_tsvector SET (parallel_workers = 2); CREATE INDEX wowidx ON test_tsvector USING gin (a); -- 2.37.1 (Apple Git-137.1)
^ permalink raw reply [nested|flat] 8+ messages in thread

* Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
  2026-10-21 18:00 BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries PG Bug reporting form <noreply@postgresql.org>
  2026-11-04 05:42 ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries shihao zhong <zhong950419@gmail.com>
  2026-11-06 07:52   ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
  2026-11-06 08:16     ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
  2026-11-08 00:02       ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries shihao zhong <zhong950419@gmail.com>
@ 2026-11-08 22:25         ` Michael Paquier <michael@paquier.xyz>
  2026-11-11 00:33           ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
  0 siblings, 1 reply; 8+ messages in thread

From: Michael Paquier @ 2026-11-08 22:25 UTC (permalink / raw)
  To: shihao zhong <zhong950419@gmail.com>; +Cc: exclusion@gmail.com; pgsql-bugs@lists.postgresql.org

On Sat, Nov 07, 2026 at 07:02:15PM -0500, shihao zhong wrote:
> v2 uses repeat() and sets the column to STORAGE
> EXTERNAL so it stays uncompressed, like toast.sql does.

This version works here, and the test is much, much cheaper than in
your v1 where most of the extra time was spent to build the long
value.  Thanks for updating the patch.

(We're in freeze period for the release, so I'll get back to it in 48
hours or so after the version tags are pushed.)
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
  2026-10-21 18:00 BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries PG Bug reporting form <noreply@postgresql.org>
  2026-11-04 05:42 ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries shihao zhong <zhong950419@gmail.com>
  2026-11-06 07:52   ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
  2026-11-06 08:16     ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
  2026-11-08 00:02       ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries shihao zhong <zhong950419@gmail.com>
  2026-11-08 22:25         ` Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries Michael Paquier <michael@paquier.xyz>
@ 2026-11-11 00:33           ` Michael Paquier <michael@paquier.xyz>
  0 siblings, 0 replies; 8+ messages in thread

From: Michael Paquier @ 2026-11-11 00:33 UTC (permalink / raw)
  To: shihao zhong <zhong950419@gmail.com>; +Cc: exclusion@gmail.com; pgsql-bugs@lists.postgresql.org

On Mon, Nov 09, 2026 at 07:25:17AM +0900, Michael Paquier wrote:
> (We're in freeze period for the release, so I'll get back to it in 48
> hours or so after the version tags are pushed.)

Applied down to v15 as of 1d657c6e013e.
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

^ permalink  raw  reply  [nested|flat] 8+ messages in thread


end of thread, other threads:[~2026-11-11 00:33 UTC | newest]

Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-10-21 18:00 BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries PG Bug reporting form <noreply@postgresql.org>
2026-11-04 05:42 ` shihao zhong <zhong950419@gmail.com>
2026-11-04 15:48   ` Ayush Tiwari <ayushtiwari.slg01@gmail.com>
2026-11-06 07:52   ` Michael Paquier <michael@paquier.xyz>
2026-11-06 08:16     ` Michael Paquier <michael@paquier.xyz>
2026-11-08 00:02       ` shihao zhong <zhong950419@gmail.com>
2026-11-08 22:25         ` Michael Paquier <michael@paquier.xyz>
2026-11-11 00:33           ` Michael Paquier <michael@paquier.xyz>

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