| 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-04-27 02:07:03 |
| Message-ID: | 1e5bb916-fd58-3995-851b-6875c6dd73eb@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 4/26/17 21:12, Andres Freund wrote:
> I think it's unacceptable to regress with an error message here. I've
> seen sequence DDL being used while concurrent DML was onging in a number
> of production use cases, and just starting to error out instead of
> properly blocking doesn't seem acceptable to me.
It's not clear to me what the use case is here that we are optimizing
for. The best solution would depend on that. Running concurrent ALTER
SEQUENCE in a tight loop is probably not it. ;-)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-04-27 05:52:11 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| Previous Message | Michael Paquier | 2017-04-27 01:51:39 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-04-27 02:10:34 | Re: StandbyRecoverPreparedTransactions recovers subtrans links incorrectly |
| Previous Message | Peter Eisentraut | 2017-04-27 02:03:24 | Re: identity columns |