| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Jason Petersen <jason(at)citusdata(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| Date: | 2017-04-25 05:43:58 |
| Message-ID: | CAB7nPqSJB1h535AcQ+ZOyqM0Sg6VORf0hL_Vrw96uvajR03hQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Tue, Apr 25, 2017 at 2:18 PM, Jason Petersen <jason(at)citusdata(dot)com> wrote:
> FWIW that was my gut read as well; take a slightly more restrictive lock,
> possibly blocking other ALTERs (unsure of prior behavior) to avoid ERROR but
> not at the cost of blocking readers. This seems about right to me.
>
> Haven't reported a bug before; what's next? Get a reviewer?
We have done everything that can be done, and for sure more review is
welcome. I have added an open item here:
https://wiki.postgresql.org/index.php?title=PostgreSQL_10_Open_Items
And that's a commit of Peter, who is also the author, now in CC, which
is causing the regression.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | K S, Sandhya (Nokia - IN/Bangalore) | 2017-04-25 13:44:49 | Re: Crash observed during the start of the Postgres process |
| Previous Message | Jason Petersen | 2017-04-25 05:18:47 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rémi Zara | 2017-04-25 05:53:02 | Re: Unportable implementation of background worker start |
| Previous Message | Michael Paquier | 2017-04-25 05:39:40 | Re: PG 10 release notes |