| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Tristan Partin <tristan(at)partin(dot)io>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add pg_stat_kind_info system view |
| Date: | 2026-07-02 00:26:23 |
| Message-ID: | CAA5RZ0tBWqed2eq3+ERBeOpLVr0gJx9Cy4D=FHt2HRfpm5E+DA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > But also, because this will be used to calculate consumption, we
> > should add a note in
> > the documentation to differentiate between live storage usage vs the
> > DSA footprint,
> > which will not be shrunk when entries are deleted. Someone may be confused
> > that their entries are much lower after deleting entries, but their memory
> > footprint is still high because the OS does not reclaim the free'd space.
> > What do you think?
>
> Hmm. I am not completely sure which way is best here. So, I think
> that I am just going to drop this field for now (entry_size as of
> latest patch), and keep the rest of the patch. It's still useful to
> me, and we could always add one or more memory-related field later as
> we feel in this release cycle.
Right. I also think this needs more discussion, and it should not hold
up everything else.
--
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2026-07-02 00:32:16 | remove switch statement in vector8_shift_{left,right} |
| Previous Message | Henson Choi | 2026-07-02 00:23:30 | Re: Row pattern recognition |