Re: [BUGS] Concurrent ALTER SEQUENCE RESTART Regression
| От | Michael Paquier |
|---|---|
| Тема | Re: [BUGS] Concurrent ALTER SEQUENCE RESTART Regression |
| Дата | |
| Msg-id | CAB7nPqTYQ+GZ9jP7FNHbTa+J5Z1k3ZmBrxvAhtOvpkH3k9j42g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [BUGS] Concurrent ALTER SEQUENCE RESTART Regression (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: [BUGS] Concurrent ALTER SEQUENCE RESTART Regression
|
| Список | pgsql-bugs |
On Thu, Apr 27, 2017 at 3:23 PM, Andres Freund <andres@anarazel.de> wrote:
> More fun:
>
> A: CREATE SEQUENCE someseq;
> A: BEGIN;
> A: ALTER SEQUENCE someseq MAXVALUE 10;
> B: SELECT nextval('someseq') FROM generate_series(1, 1000);
>
> => ignores maxvalue
Well, for this one that's because the catalog change is
transactional... I am not sure that using heap_inplace_update() would
make things better just to be compatible with previous versions.
--
Michael
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: