From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_restore load data |
Date: | 2017-11-16 21:33:03 |
Message-ID: | ae75ba0c-6222-6d2d-dbb5-0274e2ea0385@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/16/2017 03:13 PM, bricklen wrote:
>
> On Thu, Nov 16, 2017 at 1:07 PM, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net
> <mailto:ron(dot)l(dot)johnson(at)cox(dot)net>> wrote:
>
> v9.2.7 (Yes, I know, it's old. Nothing I can do about it.)
>
> During a "whole database" restore using pg_restore of a custom dump,
> when is the data actually loaded? I've looked in the list output and
> don't see any "load" statements.
>
>
> Look for COPY lines, that's how the data is restored.
$ pg_restore -l CDSHA01.dump > CDSHA01.txt
$ grep --color -i copy CDSHA01.txt
$ echo $?
1
There are lots of "restoring data", though. I should have thought to grep
for that.
One thing that puzzles me is how fast the tables (even large ones) loaded
compared to how slow the pg_dump -Fc was. Granted, I'm running -j4 but
still, these were some really large, poorly compressible tables (the dump
file was about as big as du -mc data/base).
--
World Peace Through Nuclear Pacification
From | Date | Subject | |
---|---|---|---|
Next Message | David Pacheco | 2017-11-17 00:11:16 | Re: postmaster deadlock while logging after syslogger exited |
Previous Message | melvin6925 | 2017-11-16 21:22:46 | Re: pg_restore load data |