| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Date: | 2021-06-10 18:00:17 |
| Message-ID: | 1682562.1623348017@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
"Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com> writes:
> On 2021-06-10 09:54, Ranier Vilela wrote:
>> Your cmd lacks =
>> =>pg_dumpall -U Admin --exclude-database=MailPen >zzz.sql
> 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.
[ experiments... ] Looks like you gotta do it like this:
pg_dumpall '--exclude-database="MailPen"' ...
This surprises me, as I thought it was project policy not to
case-fold command-line arguments (precisely because you end
up needing weird quoting to prevent that).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-06-10 18:14:55 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
| Previous Message | Jonathan S. Katz | 2021-06-10 17:57:42 | Re: unnesting multirange data types |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-06-10 18:23:39 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Dean Gibson (DB Administrator) | 2021-06-10 17:43:13 | Re: AWS forcing PG upgrade from v9.6 a disaster |