BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts

Поиск
Список
Период
Сортировка
От paul@salesintel.com
Тема BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts
Дата
Msg-id 20160105150227.1117.51692@wrigleys.postgresql.org
обсуждение исходный текст
Ответы Re: BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts  (Andres Freund <andres@anarazel.de>)
Список pgsql-bugs
Дерево обсуждения 
The following bug has been logged on the website:

Bug reference:      13846
Logged by:          Paul Hester
Email address:      paul@salesintel.com
PostgreSQL version: 9.5rc1
Operating system:   Windows 10 Pro
Description:

When using an INSERT statement with an ON CONFLICT clause, if there is a
conflict, and the table being inserted into has a column defaulted to
nextval('seq'), the sequencer 'seq' is always incremented. This can quickly
and artificially consume all values of the sequencer; it behaves as if
conflict detection happens after inserts are attempted, rather than before.

В списке pgsql-bugs по дате отправления:

Предыдущее
От:
Дата:
Сообщение: Re: BUG #13822: Slave terminated - WAL contains references to invalid page
Следующее
От: gnkna@yahoo.co.in
Дата:
Сообщение: BUG #13847: WARNING: skipping "pg_toast_" --- cannot vacuum indexes, views, or special system tables VACUUM