Re: Issues with upserts

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: André Hänsel <andre(at)webkr(dot)de>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Issues with upserts
Date: 2022-07-13 15:06:46
Message-ID: CAKFQuwYNmmaV_FK4CjLOW9nm-JejmPAUHfpiZ=WnSemOuhsx_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jul 13, 2022 at 7:58 AM André Hänsel <andre(at)webkr(dot)de> wrote:

>
> SELECT last_value FROM t_id_seq;
>
>
>
> This will yield “8”, showing that new sequence numbers have been generated
> for each attempt.
>

Yep, an entire able-to-be-inserted tuple is formed every time. That
requires evaluating defaults so that every column has a value.

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2022-07-13 15:13:43 Re: Issues with upserts
Previous Message Tom Lane 2022-07-13 15:06:20 Re: Issues with upserts