BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts

From: paul(at)salesintel(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts
Date: 2016-01-05 15:02:27
Message-ID: 20160105150227.1117.51692@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 13846
Logged by: Paul Hester
Email address: paul(at)salesintel(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-01-05 15:10:53 Re: BUG #13845: Incorrect week number
Previous Message Marek.Petr 2016-01-05 13:46:25 Re: BUG #13822: Slave terminated - WAL contains references to invalid page