From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: dat names generated by pg_dump |
Date: | 2018-09-03 02:22:31 |
Message-ID: | 0587ce0a-23a5-6804-9ecc-b663dd898265@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 09/02/2018 07:07 PM, Ron wrote:
> On 09/02/2018 08:41 PM, Adrian Klaver wrote:
>> On 09/02/2018 05:40 PM, Ron wrote:
>>> Hi,
>>>
>>> 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.
>>
>> Some background would be helpful:
>>
>> 1) What is producing the *.dat files?
>
> pg_dump, as described in the Subject.
Oops, missed that.
>
>>
>> 2) What is their structure?
>
> They're pg_dump files.
What is the full pg_dump command used?
>
>>
>> 3) What do the numbers refer to?
>
> That's what I'm asking the list.
>
>>
>>>
>>> If relevant, the source database is v8.4, but the backup was done by
>>> 9.6 on a separate server.
>>>
>>> $ ls -1 CDSLBXW/*dat | head
>>> CDSLBXW/8412.dat
>>> CDSLBXW/8414.dat
>>> CDSLBXW/8416.dat
>>> CDSLBXW/8418.dat
>>> CDSLBXW/8420.dat
>>> CDSLBXW/8422.dat
>>> CDSLBXW/8423.dat
>>> CDSLBXW/8425.dat
>>> CDSLBXW/8427.dat
>>> CDSLBXW/8428.dat
>>>
>>> Thanks
>>>
>>
>>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-09-03 02:26:12 | Re: dat names generated by pg_dump |
Previous Message | Ron | 2018-09-03 02:07:58 | Re: dat names generated by pg_dump |