From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: dat names generated by pg_dump |
Date: | 2018-09-03 02:47:35 |
Message-ID: | a5c966c4-1de1-dfb0-8fca-042f987344f4@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 09/02/2018 09:26 PM, Tom Lane wrote:
> Ron <ronljohnsonjr(at)gmail(dot)com> writes:
>> I can associate these dat names with their source tables through a bunch of
>> bash and vim manual operations, but I was wondering if there's any automated
>> method (maybe some SQL query of some catalog table; pg_class didn't seem to
>> have the relevant data) of making the association.
> Those numbers are the "dump object IDs" generated by pg_dump. They don't
> have any significance on the server side, and typically would vary from
> one pg_dump run to another. You have to look at the dump TOC (table of
> contents) to figure out what corresponds to what. For example,
>
> $ pg_dump -Fd -f dumpd regression
> $ ls -1 dumpd
> 6143.dat.gz
> 6144.dat.gz
> 6145.dat.gz
> ...
> blob_3001.dat.gz
> blobs.toc
> toc.dat
> $ pg_restore -l dumpd
> ;
> ; Archive created at 2018-09-02 22:14:48 EDT
> ...
> 6573; 2613 119655 BLOB - 119655 postgres
Thanks. That's exactly what I needed.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-09-03 03:04:19 | Re: WARNING: could not flush dirty data: Function not implemented |
Previous Message | Tom Lane | 2018-09-03 02:26:12 | Re: dat names generated by pg_dump |