Re: Remove superuser() checks from pgstattuple

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>,Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>,"pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove superuser() checks from pgstattuple
Date: 2016-09-05 01:35:29
Message-ID: 149FA18A-C7B2-407C-B433-EAAFA97DF302@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On September 4, 2016 6:33:30 PM PDT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Andres Freund <andres(at)anarazel(dot)de> writes:
>> On 2016-09-04 21:09:41 -0400, Tom Lane wrote:
>>> Hm, couldn't we do that automatically? At least in the case where
>only
>>> one base-version script is available?
>
>> You mean determining the baseversion? Hm, yes, that might work. But
>I'm
>> not sure how much we can rely on no earlier scripts being already
>> installed or such. Seems like a problem you'd possibly only encounter
>in
>> the field or dirty development environments.
>
>Actually, why would we care? Pick one, with some tiebreaker rules
>(shortest update path, for starters).

Fair point.

> I think nearly all of the
>infrastructure for this is already there in extension.c.

Yes, it doesn't sound very hard...

Andres

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mithun Cy 2016-09-05 02:29:02 Re: Patch: Implement failover on libpq connect level.
Previous Message Tom Lane 2016-09-05 01:33:30 Re: Remove superuser() checks from pgstattuple