Re: [HACKERS] [BUGS] Concurrent ALTER SEQUENCE RESTART Regression - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] [BUGS] Concurrent ALTER SEQUENCE RESTART Regression
Date
Msg-id CA+TgmoYQ_RAJbyupefJsg2W2P4vjKfCuLHyuqOuX_54SNCA9DQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [BUGS] Concurrent ALTER SEQUENCE RESTART Regression  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] [BUGS] Concurrent ALTER SEQUENCE RESTART Regression  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Wed, May 24, 2017 at 9:04 AM, Andres Freund <andres@anarazel.de> wrote:
> At the very least we'll have to error out. That's still not nice usability wise, but it sure beats returning flat out
wrongvalues.
 

I'm not sure.  That seems like it might often be worse.  Now you need
manual intervention before anything even has a hope of working.

> I suspect that the proper fix would be to use a different relfilenode after ddl, when changing the seq file itself
(I.e.setval and restart).  That seems like it'd be architecturally more appropriate, but also some work.
 

I can see some advantages to that, but it seems far too late to think
about doing that in v10.

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



pgsql-hackers by date:

Previous
From: Nick Dro
Date:
Subject: [HACKERS] Error log for psql (uploading backup) in PostgreSQL 9.3.17
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Error-like LOG when connecting with SSL for password authentication