Re: pg_upgrade failing for 200+ million Large Objects

From: Jan Wieck <jan(at)wi3ck(dot)info>
To: Zhihong Yu <zyu(at)yugabyte(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: 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 23:18:33
Message-ID: 3886649c-c77d-dfd7-08a4-d1606bc71254@wi3ck.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/22/21 5:36 PM, Zhihong Yu wrote:
> 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.

You are right. I will fix that.

Thanks, Jan

--
Jan Wieck
Principle Database Engineer
Amazon Web Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2021-03-22 23:35:09 Re: proposal - psql - use pager for \watch command
Previous Message Tom Lane 2021-03-22 23:18:11 Re: Allow an alias to be attached directly to a JOIN ... USING