Re: BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts
Date: 2016-01-06 19:26:32
Message-ID: n6jppa$6kl$1@ger.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Paul Hester schrieb am 06.01.2016 um 06:04:
> This limitation, of consuming sequencers used for defaults on columns
> not necessary to resolve conflict, diminishes the viability for using
> Postges UPSERTS for large data warehouses, is all I'm saying (or
> requires surrogate keys being 64 bit). Just caught me by surprise in
> comparison to other RDBMSs offering some form of UPSERTs that would
> not consume a sequencer if its values weren't required to resolve
> conflicts.

Why does this "diminish" the viability of a sequence?

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2016-01-06 19:53:04 Re: pg_regress --help missing description of --bindir
Previous Message Navaneethakrishnan Gopal 2016-01-06 18:36:51 Re: BUG #13847: WARNING: skipping "pg_toast_" --- cannot vacuum indexes, views, or special system tables VACUUM