Re: [HACKERS] pg_shmem_allocations view

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marti Raudsepp <marti(at)juffo(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] pg_shmem_allocations view
Date: 2019-11-15 19:43:09
Message-ID: CA+TgmoatV1iTeo_jdixJv0cuDHwzi3ysJhw+CUDOtxf7vToOOA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 5, 2016 at 7:01 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Here's a rebased version. I remember why I didn't call the column
> "offset" (as Michael complained about upthread), it's a keyword...

This never got applied, and that annoyed me again today, so here's a
new version that I've whacked around somewhat and propose to commit. I
ripped out the stuff pertaining to dynamic shared memory segments,
both because I think it might need some more thought and discussion,
and because the part the pertains to the main shared memory segment is
the part I keep wishing we had. We can add that other part later if
we're all agreed on it, but let's go ahead and add this part now.

Other things I changed:
- Doc edits.
- Added REVOKE statements as proposed by Michael (and I agree).
- Can't patch pg_proc.h any more, gotta patch pg_proc.dat.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment Content-Type Size
0001-Add-a-pg_shmem_allocations-view.patch application/octet-stream 9.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-11-15 19:58:22 Re: [HACKERS] pg_shmem_allocations view
Previous Message Pavel Stehule 2019-11-15 19:14:17 Re: jsonb_set() strictness considered harmful to data