Re: pg_stat_statements: improve loading and saving routines for the dump file - Mailing list pgsql-hackers

From Ivan Kush
Subject Re: pg_stat_statements: improve loading and saving routines for the dump file
Date
Msg-id e3071cfc-7a9e-4476-81fd-8ff1095baabd@tantorlabs.com
Whole thread Raw
In response to Re: pg_stat_statements: improve loading and saving routines for the dump file  (Ivan Kush <ivan.kush@tantorlabs.com>)
Responses Re: pg_stat_statements: improve loading and saving routines for the dump file
Re: pg_stat_statements: improve loading and saving routines for the dump file
List pgsql-hackers
What does this patch give on aglobal scale? Does it save much memory or 
increase performance? How many times?

On 1/21/25 13:51, m.litsarev@postgrespro.ru wrote:
>> // Mutex should be last field, as this field isn't copied to dump file
> Updated.
>
>> 2) You didn't take into account the upgrade. Saved in Postgres with 
>> this byte and try to load in version without this byte.
> The PGSS_DUMP_FILE format is defined by PGSS_FILE_HEADER magic number 
> (the first four bytes in the dump file). Once they does not coinside 
> (when the file is being read) the statistics are not loaded from the 
> dump file and set to zero and the irrelevant dump file is skipped. 
> This is the actual behaviour implemented in the code.
>
> Respectfully,
>
> Mikhail Litsarev,
> Postgres Professional: https://postgrespro.com

-- 
Best wishes,
Ivan Kush
Tantor Labs LLC




pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: Statistics Import and Export
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Add roman support for to_number function