Re: pg_shmem_allocations view

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_shmem_allocations view
Date: 2014-05-06 21:04:04
Message-ID: CA+U5nMK+Pn-+BTzFzw44dKr0dyy3B8gBtRUDfKHJ00xaOR31HA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6 May 2014 20:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Tue, May 6, 2014 at 2:34 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> FWIW, I vote for fixing (a) now but holding (b) for 9.5.
>
>> I guess I'll vote for applying both. I don't see a lot of risk, and I
>> think doing one with out the other is somewhat pointless.
>
> The difference is that there's not consensus about the details of the
> views ... as borne out by your next paragraph.
>
> Now admittedly, we could always redefine the views in 9.5, but
> I'd rather not be doing this sort of thing in haste. Something
> as user-visible as a system view really ought to have baked awhile
> before we ship it. Patch (a) is merely institutionalizing the
> expectation that DSM segments should have names, which is a much
> lower-risk bet.

As long as all the functions are exposed to allow b) to run as an
extension, I don't see we lose anything by waiting a while.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-05-06 21:05:00 Re: [COMMITTERS] pgsql: pgindent run for 9.4
Previous Message Tomas Vondra 2014-05-06 21:01:39 Re: Sending out a request for more buildfarm animals?