Subject: Re: Fix pg_upgrade to preserve datdba
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Magnus Hagander <magnus@hagander.net>,
 Robins Tharakan <tharakan@gmail.com>,
 Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
References: <a9f9376f1c3343a6bb319dce294e20ac@EX13D05UWC001.ant.amazon.com>
 <CABUevEwyLb9VE0D+bAQtUnaA7bffXYzBpopYuh7kGTQxY9T5_g@mail.gmail.com>
 <CAEP4nAw2WA1wyb9LG7BOEuN3Xr-xWiZZ0w_hKtpyvdUPKmcAJA@mail.gmail.com>
 <1742698.1615221182@sss.pgh.pa.us>
 <CABUevEzvU07CqwGdaOmxNfDtrkY-xEcLjiN3GAmurowyCnbG7w@mail.gmail.com>
 <1743618.1615222719@sss.pgh.pa.us>
 <4fbf92f2-ec91-f4fa-a259-f0968e34f3d7@wi3ck.info>
 <0b5d506d-70d2-1506-bbdf-89e6453c0289@wi3ck.info>
 <384713.1616345832@sss.pgh.pa.us>
 <2284b71d-af55-2625-f8c2-cedf1f1a70ca@wi3ck.info>
 <ff77882d-1b1f-1735-402a-f4583f1b2f58@wi3ck.info>
 <388155.1616351018@sss.pgh.pa.us> <388710.1616351698@sss.pgh.pa.us>
From: Jan Wieck <jan@wi3ck.info>
Message-ID: <ea5bebf7-683e-f183-ebd7-98d9a552e18c@wi3ck.info>
Date: Sun, 21 Mar 2021 15:36:51 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <388710.1616351698@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/ea5bebf7-683e-f183-ebd7-98d9a552e18c%40wi3ck.info>
Precedence: bulk

On 3/21/21 2:34 PM, Tom Lane wrote:
> and I see
> 
> --
> -- Name: joe; Type: DATABASE; Schema: -; Owner: joe
> --
> 
> CREATE DATABASE joe WITH TEMPLATE = template0 ENCODING = 'SQL_ASCII' LOCALE = 'C';
> 
> 
> ALTER DATABASE joe OWNER TO joe;
> 
> so at least in this case it's doing the right thing.  We need a bit
> more detail about the context in which it's doing the wrong thing
> for you.

After moving all of this to a pristine postgresql.org based repo I see 
the same. My best guess at this point is that the permission hoops, that 
RDS and Aurora PostgreSQL are jumping through, was messing with this. 
But that has nothing to do with the actual topic.

So let's focus on the actual problem of running out of XIDs and memory 
while doing the upgrade involving millions of small large objects.


Regards, Jan


-- 
Jan Wieck
Principle Database Engineer
Amazon Web Services