Re: Concurrent ALTER SEQUENCE RESTART Regression

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

To: Michael Paquier <michael.paquier@gmail.com>, Petr Jelinek <petr.jelinek@2ndquadrant.com>

Cc: Andres Freund <andres@anarazel.de>, Jason Petersen <jason@citusdata.com>, PostgreSQL mailing lists <pgsql-bugs@postgresql.org>

Date: 2017-05-02T14:37:07Z

Lists: pgsql-bugs, pgsql-hackers

On 4/30/17 08:30, Michael Paquier wrote:
> Also, the docs
> still mention that changes take immediately effect and ALTER SEQUENCE
> changes are non-reversible.

Fixed that.

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

Commits

Make ALTER SEQUENCE, including RESTART, fully transactional.
- 3d79013b970d 10.0 landed
Modify sequence catalog tuple before invoking post alter hook.
- 665104557fdc 10.0 landed
Use weaker locks when updating pg_subscription_rel
- 521fd4795e3e 10.0 cited
Add pg_sequence system catalog
- 1753b1b02703 10.0 cited
Modify sequence state storage to eliminate dangling-pointer problem
- a2597ef17958 7.3.1 cited