| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Add memory context type to pg_backend_memory_contexts view |
| Date: | 2024-04-16 01:30:01 |
| Message-ID: | CAApHDvrXX1OR09Zjb5TnB0AwCKze9exZN=9Nxxg1ZCVV8W-3BA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
In [1] Andres mentioned that there's no way to determine the memory
context type in pg_backend_memory_contexts. This is a bit annoying as
I'd like to add a test to exercise BumpStats().
Having the context type in the test's expected output helps ensure we
are exercising BumpStats() and any future changes to the choice of
context type in tuplesort.c gets flagged up by the test breaking.
It's probably too late for PG17, but I'll leave this here for the July CF.
David
[1] https://www.postgresql.org/message-id/20240415225749.xg7uq2hwuq2qmwpg@awork3.anarazel.de
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Add-context-type-field-to-pg_backend_memory_conte.patch | text/plain | 7.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-04-16 01:33:34 | Re: Bugs in ecpg's macro mechanism |
| Previous Message | Jeff Davis | 2024-04-16 01:23:21 | Re: Differential code coverage between 16 and HEAD |