From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Cc: | Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Has the Update savepoint example outlived its usefulness? |
Date: | 2021-06-24 16:02:53 |
Message-ID: | CAKFQuwZedFYe6pMOD6bbPiWEiGqTU0wNQLmCVn8HKeUTRH64tQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thu, Jun 24, 2021 at 4:20 AM Peter Eisentraut <
peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> On 04.06.21 02:08, David G. Johnston wrote:
> > The example in the update documentation that does an upsert using a
> > savepoint seems like it should just go away now that we have insert...on
> > conflict. Making an explicit reference (and link) to that feature in
> > the Update documentation should be added in its place (well, under
> notes).
>
> Do we need to replace it by a different example then?
>
I don't think so. The example that replaces it already exists on the
INSERT documentation page, we just need to remove this example on the
UPDATE page and point the user there instead.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2021-06-24 19:53:29 | Re: 24.1.5.1. Multixacts And Wraparound |
Previous Message | Peter Eisentraut | 2021-06-24 11:24:01 | Re: Cities name column name inconsistent |