| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Add CONCURRENTLY option to REPACK |
| Date: | 2026-06-16 12:30:02 |
| Message-ID: | ajFBgQ9GtyIulWmK@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Hi,
On 2026-Apr-07, Aleksander Alekseev wrote:
> 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?
Yeah, that's a reasonable idea. I have added the check, thanks.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"No me acuerdo, pero no es cierto. No es cierto, y si fuera cierto,
no me acuerdo." (Augusto Pinochet a una corte de justicia)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2026-06-16 16:35:02 | pgsql: logical decoding: Correctly free speculative insertion |
| Previous Message | Álvaro Herrera | 2026-06-16 12:28:39 | pgsql: concurrent repack: check there are no leftover toast attribs |