pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dean Gibson (DB Administrator) <postgresql@mailpen.com>
To: pgsql-performance@postgresql.org
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
Date: Thu, 10 Jun 2021 09:07:52 -0700
Message-ID: <ec18a226-6bef-7ba6-e176-c751e189270d@mailpen.com> (raw)
In-Reply-To: <18f77a0c-dade-b86a-cbeb-6f85d3d137e1@dunslane.net>
References: <88dec70b-eb63-0b72-0b5d-253851ef127b@mailpen.com>
	<92cc8563-195f-8727-d887-5f2bb63f231f@mailpen.com>
	<20210601041635.GQ2082@telsasoft.com>
	<a38c45cf-3bbd-b43a-0f8a-11539c1c6dc1@mailpen.com>
	<a7e9da9d-7433-ee02-9e35-db6b19acdcd4@mailpen.com>
	<18f77a0c-dade-b86a-cbeb-6f85d3d137e1@dunslane.net>

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?

view thread (54+ messages)  latest in thread

Message-ID: <ec18a226-6bef-7ba6-e176-c751e189270d@mailpen.com>
Permalink:  ../ec18a226-6bef-7ba6-e176-c751e189270d@mailpen.com/
Also on:    postgresql.org/message-id/ec18a226-6bef-7ba6-e176-c751e189270d@mailpen.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: postgresql@mailpen.com
  Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
  In-Reply-To: <ec18a226-6bef-7ba6-e176-c751e189270d@mailpen.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox