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 17:43:13
Message-ID: 4abbbebd-1496-7376-136f-38eb91773cd2@mailpen.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

On 2021-06-10 09:54, Ranier Vilela wrote:
> Em qui., 10 de jun. de 2021 às 13:08, Dean Gibson (DB Administrator)
> <postgresql(at)mailpen(dot)com <mailto:postgresql(at)mailpen(dot)com>> escreveu:
>
>
> 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?
>
> See at:
> https://www.postgresql.org/docs/13/app-pg-dumpall.html
> <https://www.postgresql.org/docs/13/app-pg-dumpall.html>
>
> Your cmd lacks =
> =>pg_dumpall -U Admin --exclude-database=MailPen >zzz.sql
>
> regards, Ranier Vilela

I read that before posting, but missed that.  Old command line patterns
die hard!

However, the result was the same:  3.5GB before running out of space.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2021-06-10 17:57:42 Re: unnesting multirange data types
Previous Message Peter Geoghegan 2021-06-10 17:42:47 Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2021-06-10 18:00:17 Re: AWS forcing PG upgrade from v9.6 a disaster
Previous Message Vijaykumar Jain 2021-06-10 16:58:59 Re: waiting for client write