Re: In-order pg_dump (or in-order COPY TO) - Mailing list pgsql-general

From Tom Lane
Subject Re: In-order pg_dump (or in-order COPY TO)
Date
Msg-id 366773.1756749256@sss.pgh.pa.us
Whole thread Raw
In response to Re: In-order pg_dump (or in-order COPY TO)  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: In-order pg_dump (or in-order COPY TO)
List pgsql-general
Adrian Klaver <adrian.klaver@aklaver.com> writes:
> I did some digging in the code and see that the TOC is more then that, 
> it stores a range of data. Still have not part where the offsets are 
> ignored for writes to stdout, but will keep on digging.

The TOC is initially written out with zeroes for the offsets.
Then the per-table data parts are written out, tracking where
each one begins.  At the end, if the output file is seekable,
pg_dump seeks back to the start and re-writes the whole TOC
section, now with data offsets populated.  But output to a
pipe won't be seekable.

            regards, tom lane



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: In-order pg_dump (or in-order COPY TO)
Next
From: Adrian Klaver
Date:
Subject: Re: In-order pg_dump (or in-order COPY TO)