Re: Concurrent ALTER SEQUENCE RESTART Regression

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jason Petersen <jason(at)citusdata(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Concurrent ALTER SEQUENCE RESTART Regression
Date: 2017-06-16 16:15:55
Message-ID: 3fc03672-5437-713b-b49e-d2e93779dc96@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 6/14/17 13:58, Robert Haas wrote:
> On Tue, Jun 13, 2017 at 3:04 PM, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> On 5/2/17 12:45, Robert Haas wrote:
>>> Another thing that doesn't look so good about AlterSequence is that it
>>> uses RangeVarGetRelid() instead of RangeVarGetsRelidExtended() with
>>> RangeVarCallbackOwnsRelation or some derivative thereof. That of
>>> course means you can obstruct access to a sequence you don't own.
>>
>> Here is a patch for this. Note that this is old code, but it seems
>> worth fixing now while we're at it.
>
> +1.

committed

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message konst583 2017-06-16 19:56:17 BUG #14710: Function now() and logical replication
Previous Message Константин Евтеев 2017-06-16 13:13:36 Re: BUG #14699: Statement trigger and logical replication

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2017-06-16 16:46:00 Re: Broken hint bits (freeze)
Previous Message David Fetter 2017-06-16 16:07:30 Re: ASOF join