From: | Edwin UY <edwin(dot)uy(at)gmail(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Question about pg_dump + pg_restore + pg_toast |
Date: | 2025-03-02 09:45:30 |
Message-ID: | CA+wokJ-N5KZ=bSNrVnOz_NS9zGofbZu1HijLq9QzmTpb87XN6Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Yeah tried to do the pg_dump, 8 hours down the line, not even halfway done.
As expected, it is stuck on the way with the largest toast.
pg_dump -v -d [database] -U [user] \
-h [hostname] \
--if-exists --clean -Fc \
-f [dumpfile] \
--quote-all-identifiers -n [schemaname]
Will try the -Fd and -j option.
On Sun, Mar 2, 2025 at 1:40 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
> On Sat, Mar 1, 2025 at 4:27 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Edwin UY <edwin(dot)uy(at)gmail(dot)com> writes:
>> > If need be, do I manually edit the dumpfile using something like vi?
>>
>> That's usually the last-ditch answer. Often you can just feed the
>> script to psql and ignore any errors, though.
>
>
> Single-threaded text is pretty slow for a 500GB database.
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>
From | Date | Subject | |
---|---|---|---|
Next Message | kaido vaikla | 2025-03-03 13:50:19 | pg_upgrade and generated column |
Previous Message | Laurenz Albe | 2025-03-02 06:39:13 | Re: Question about pg_dump + pg_restore + pg_toast |