| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | 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-04-27 01:07:20 |
| Message-ID: | 99a009ea-1797-5b82-f3d3-eb4a5a8eb5dc@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 4/26/17 19:12, Michael Paquier wrote:
> Well, there are more DDL commands where it is possible to see "tuple
> concurrently updated" easily, an example is ALTER ROLE. So nothing is
> concurrent-proof with this code and I think needs a careful lookup
> because this error should never be something that is user-visible.
Yeah, it's been like this since time immemorial, so I don't think we
need a last minute fix now.
One thing we could do, since all catalog updates now go through
CatalogTupleUpdate(), is not use simple_heap_update() there but do the
heap_update() directly and provide a better user-facing error message.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-04-27 01:12:58 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| Previous Message | Amit Langote | 2017-04-27 00:16:06 | Re: [BUGS] BUG #14629: ALTER TABLE VALIDATE CONSTRAINTS does not obey NO INHERIT clause |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-04-27 01:10:33 | Re: Unportable implementation of background worker start |
| Previous Message | Robert Haas | 2017-04-27 00:58:31 | Re: Unportable implementation of background worker start |