| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | 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-05-02 15:05:38 |
| Message-ID: | 87b349c1-3384-437e-01d3-173a69baf46f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 4/27/17 01:52, Andres Freund wrote:
> In contrast to <v10, the actual change of the tuple is *not* happening
> with the page lock held. But now we do log XLOG_SEQ_LOG, then unlock
> the buffer, and then do a CatalogTupleUpdate(). How is that correct?
The change to the sequence data and the change to the catalog are two
separate operations. There is no need AFAICT for the latter to be done
while the former is locked or vice versa.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-05-02 15:07:44 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| Previous Message | Peter Eisentraut | 2017-05-02 14:53:19 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-05-02 15:07:44 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| Previous Message | Peter Eisentraut | 2017-05-02 14:53:19 | Re: Concurrent ALTER SEQUENCE RESTART Regression |