Postgres Pro
Downloads
Home   >   mailing lists

BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts - Mailing list pgsql-bugs

From paul@salesintel.com
Subject BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts
Date
Msg-id 20160105150227.1117.51692@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts
List pgsql-bugs
Tree view 
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 by date:

Previous
From:
Date:
Subject: Re: BUG #13822: Slave terminated - WAL contains references to invalid page
Next
From: gnkna@yahoo.co.in
Date:
Subject: BUG #13847: WARNING: skipping "pg_toast_" --- cannot vacuum indexes, views, or special system tables VACUUM