| From: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Subject: | Re: pgsql: Add CONCURRENTLY option to REPACK |
| Date: | 2026-04-07 15:24:28 |
| Message-ID: | CAJ7c6TMSF7cANU8nEJ9E28EvU74tE4H7AzT292Rt3ZuHqqxq8w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Hi Alvaro,
> Add CONCURRENTLY option to REPACK
>
> [...]
I noticed that restore_tuple() checks for an insufficient number of
attributes stored separately, but doesn't check for an unlikely event
when there are too many attributes. I don't think this is intentional.
Any chance we want to fix this?
--
Best regards,
Aleksander Alekseev
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Use-stricter-checks-in-restore_tuple.patch | text/x-patch | 865 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-04-07 17:59:42 | pgsql: Allow retrieving x86 TSC frequency/flags from CPUID |
| Previous Message | Jacob Champion | 2026-04-07 15:18:35 | pgsql: libpq: Split PGOAUTHDEBUG=UNSAFE into multiple options |