| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Michael Zhilin <m(dot)zhilin(at)postgrespro(dot)ru>, pgsql-bugs(at)postgresql(dot)org, Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru> |
| Subject: | Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum |
| Date: | 2024-01-26 07:00:00 |
| Message-ID: | 0b535249-a00c-a38a-85f6-d5a38c62dd55@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi Andrey,
23.01.2024 21:09, Andrey M. Borodin wrote:
> PFA draft fixes for both this errors. Alexander, Michael, Jian, what do you think?
>
> I did not touch anything in first step - fix for original bug in this thread. However, I think that comments from Jian He worth incorporating into the fix.
>
I''m confused by a NOTICE added, as it printed now even for cases, which
worked before, for example:
CREATE TABLE t(f1 text);
CREATE INDEX idx ON t(f1);
INSERT INTO t VALUES(repeat('1234567890', 1000));
SELECT bt_index_check('idx', true);
NOTICE: Index contain tuples that cannot fit into index page, if toasted with current toast policy
bt_index_check
----------------
(1 row)
Best regards,
Alexander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-01-26 09:22:41 | Re: Fwd: BUG #18016: REINDEX TABLE failure |
| Previous Message | Tender Wang | 2024-01-26 06:21:12 | Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self |