Re: DELETING then INSERTING record with same PK in the same TRANSACTION

From: Andrew Hardy <andrew(dot)hardy(at)sabstt(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: DELETING then INSERTING record with same PK in the same TRANSACTION
Date: 2022-02-09 20:01:59
Message-ID: CAKxhU8ja0_wzsfK2er1w-moL3n0P=4ETNP4VbuFgjUknyFoROQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Really appreciate the input thank you.

I shall try to provide a full script, I guess if the cascades are relevant
in going to have to also provide all of the indirect table creations and
all of the earlier inserts to those various tables.

At the very least I'll try to provide a fuller error message and a minimum
structure that will cause it to occur.

Andrew

On Wed, 9 Feb 2022, 19:26 David G. Johnston, <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Wed, Feb 9, 2022 at 11:12 AM Andrew Hardy <andrew(dot)hardy(at)sabstt(dot)com>
> wrote:
>
>> Do I need some particular kind of settings on my transaction to be able
>> to delete and insert afresh in the same transaction?
>>
>
> No. I cannot reproduce your claim with a trivial example on stock 13.5.
>
> You will need to be less vague and at least provide an exact reproducer
> script.
>
> In case it is relevant - the first delete will lead to cascaded deletes on
>> children.
>>
>
> This may indeed be relevant. Again, you need to provide an exact
> reproducer, not expect others to reverse-engineer one for you.
>
> David J.
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2022-02-09 20:05:03 Re: DELETING then INSERTING record with same PK in the same TRANSACTION
Previous Message David G. Johnston 2022-02-09 19:26:34 Re: DELETING then INSERTING record with same PK in the same TRANSACTION