| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Ali Akbar <the(dot)apaan(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, rmt(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL |
| Date: | 2025-07-04 16:21:31 |
| Message-ID: | 202507041621.fs23x5filgko@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-Jul-03, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > On 2025-Jul-03, Justin Pryzby wrote:
> >>> Actually I think we should consider backporting to all live versions
>
> >> If you don't backpatch it, there's no point.
>
> > Oh yeah, you're absolutely right.
>
> No, it'd still be useful for handling upgrades from $busted_version
> to current. But it seems also useful in the back branches, so
> +1 for back-patch.
Pushed to all branches.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"El miedo atento y previsor es la madre de la seguridad" (E. Burke)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-07-04 16:26:29 | Re: [PATCH] Allow parallelism for plpgsql return expression after commit 556f7b7 |
| Previous Message | Álvaro Herrera | 2025-07-04 16:20:37 | Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL |