Re: pg_upgrade failing for 200+ million Large Objects

From: Zhihong Yu <zyu(at)yugabyte(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Jan Wieck <jan(at)wi3ck(dot)info>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Robins Tharakan <tharakan(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade failing for 200+ million Large Objects
Date: 2021-03-22 21:36:38
Message-ID: CALNJ-vSPnudYcS8YowHeq7VAf7PBRyu0vpsbmb_VvTJgguVyHA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> Hi,
>
w.r.t. pg_upgrade_improvements.v2.diff.

+ blobBatchCount = 0;
+ blobInXact = false;

The count and bool flag are always reset in tandem. It seems
variable blobInXact is not needed.

Cheers

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message isabelle Ross 2021-03-22 21:47:07 tool to migrate database
Previous Message Justin Pryzby 2021-03-22 21:13:29 Re: UPDATE ... SET (single_column) = row_constructor is a bit broken from V10 906bfcad7ba7c