Re: Statistics Import and Export - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Statistics Import and Export
Date
Msg-id Z9gwfFP-eTx-MTqr@nathan
Whole thread Raw
In response to Re: Statistics Import and Export  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: Statistics Import and Export
List pgsql-hackers
On Sun, Mar 16, 2025 at 05:32:15PM -0400, Corey Huinker wrote:
>>
>> * The custom format actually does two WriteToc() calls, and since these
>>   patches move the queries to this part of pg_dump, it means we'll run all
>>   the queries twice.  The comments around this code suggest that the second
>>   pass isn't strictly necessary and that it is really only useful for
>>   data/parallel restore, so we could probably skip it for no-data dumps.
>>
> 
> Is there any reason we couldn't have stats objects remove themselves from
> the list after completion?

I'm assuming that writing a completely different TOC on the second pass
would corrupt the dump file.  Perhaps we could teach it to skip stats
entries on the second pass or something, but I'm not too wild about adding
to the list of invasive changes we're making last-minute for v18.

-- 
nathan



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: Patch: Cover POSITION(bytea,bytea) with tests
Next
From: Andrew Dunstan
Date:
Subject: Re: plperl version on the meson setup summary screen