Re: AWS forcing PG upgrade from v9.6 a disaster

From: "Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
Date: 2021-06-10 16:07:52
Message-ID: ec18a226-6bef-7ba6-e176-c751e189270d@mailpen.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

On 2021-06-10 03:29, Andrew Dunstan wrote:
> On 6/9/21 9:50 PM, Dean Gibson (DB Administrator) wrote:
>> First, pg_dumpall (v13.3) errors out, because on RDS, you cannot be a superuser, & it tries to dump protected stuff.  If there is a way around that, I'd like to know it, even though it's not an issue now. pg_dump works OK, but of course you don't get the roles dumped. Fortunately, I kept script files that have all the database setup, so I just ran them to create all the relationships, & then used the pg_dump output.  Worked flawlessly.
> This was added in release 12 specifically with RDS in mind:
>
>   pg_dumpall --exclude-database
>
> cheers, andrew

I guess I don't understand what that option does:

=>pg_dumpall -U Admin --exclude-database MailPen >zzz.sql
pg_dump: error: could not write to output file: No space left on device
pg_dumpall: error: pg_dump failed on database "MailPen", exiting

I expected a tiny file, not 3.5GB.  "MailPen" is the only database
(other than what's pre-installed).  Do I need quotes on the command line?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2021-06-10 16:20:48 Re: RFC: Logging plan of the running query
Previous Message Tom Lane 2021-06-10 16:04:20 Re: "an SQL" vs. "a SQL"

Browse pgsql-performance by date

  From Date Subject
Next Message Ranier Vilela 2021-06-10 16:54:55 Re: AWS forcing PG upgrade from v9.6 a disaster
Previous Message Jeff Janes 2021-06-10 15:40:01 Re: waiting for client write