From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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:23:39 |
Message-ID: | a1916786-21e4-e336-47d6-71057a45ded0@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On 6/10/21 2:00 PM, Tom Lane wrote:
> "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).
>
>
Ouch. That looks like a plain old bug. Let's fix it. IIRC I just used
the same logic that we use for pg_dump's --exclude-* options, so we need
to check if they have similar issues.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-06-10 18:50:52 | Re: logical replication of truncate command with trigger causes Assert |
Previous Message | Alvaro Herrera | 2021-06-10 18:14:55 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Gibson (DB Administrator) | 2021-06-10 19:29:05 | Re: AWS forcing PG upgrade from v9.6 a disaster |
Previous Message | Tom Lane | 2021-06-10 18:00:17 | Re: AWS forcing PG upgrade from v9.6 a disaster |