Re: Concurrent ALTER SEQUENCE RESTART Regression

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, 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-05-02 14:37:07
Message-ID: efb9daf3-29fd-de6c-92ae-09c663bf7541@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2017-05-02 14:53:19 Re: Concurrent ALTER SEQUENCE RESTART Regression
Previous Message Haribabu Kommi 2017-05-02 13:20:29 Re: BUG #14635: Query is executed slower on hot standby slave database then on master database

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-05-02 14:37:27 Re: Logical replication in the same cluster
Previous Message Petr Jelinek 2017-05-02 14:14:23 Re: logical replication syntax (was DROP SUBSCRIPTION, query cancellations and slot handling)