From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Pluggable cumulative statistics |
Date: | 2024-07-09 01:45:05 |
Message-ID: | ZoyWIVHk57s9mRcS@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 08, 2024 at 07:22:32AM +0000, Bertrand Drouvot wrote:
> Yeah, what I meant to say is that one could think for example that's the
> PgStatShared_Archiver size while in fact it's the PgStat_ArchiverStats size.
> I think it's more confusing when writing the stats. Here we are manipulating
> "snapshot" and "snapshot" offsets. It was not that confusing when reading as we
> are manipulating "shmem" and "shared" offsets.
>
> As I said, the code is fully correct, that's just the wording here that sounds
> weird to me in the "snapshot" context.
After sleeping on it, I can see your point. If we were to do the
(shared_data_len -> stats_data_len) switch, could it make sense to
rename shared_data_off to stats_data_off to have a better symmetry?
This one is the offset of the stats data in a shmem entry, so perhaps
shared_data_off is OK, but it feels a bit inconsistent as well.
> Except the above (which is just a Nit), 0001 LGTM.
Thanks, I've applied 0001 for now to improve the serialization of this code.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2024-07-09 01:53:17 | Re: array_in sub function ReadArrayDimensions error message |
Previous Message | Peter Smith | 2024-07-09 01:44:10 | Re: Pgoutput not capturing the generated columns |