| From: | Jan Wieck <jan(at)wi3ck(dot)info> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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: Fix pg_upgrade to preserve datdba |
| Date: | 2021-03-21 19:36:51 |
| Message-ID: | ea5bebf7-683e-f183-ebd7-98d9a552e18c@wi3ck.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthijs van der Vleuten | 2021-03-21 19:41:47 | [PATCH] In psql \?, add [+] annotation where appropriate |
| Previous Message | Justin Pryzby | 2021-03-21 19:30:04 | Re: Different compression methods for FPI |