On Tue, Apr 25, 2017 at 4:52 AM, Jason Petersen <jason@citusdata.com> wrote:
> While I understand the above workload is nonsensical, given the non-transactional behavior of ALTER SEQUENCE
statements,previous PostgreSQL versions did not produce an error. It is likely applications have been coded with that
assumptionand will not deal well with the new behavior.
Yes, that's a bug.
> Having poked around the code a bit, I see the functions to access for sequence state have changed; I’m assuming this
isan unintended side-effect of that change.
>
> I haven’t worked up a patch myself, but I have some hope someone more familiar with the underlying changes could make
quickwork of this.
I am working on it, will send a patch soon. My first intuition is that
this is some wild lock issue. I am checking as well other code paths.
An open item has been added for the time being.
--
Michael
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
