Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self

From: Tender Wang <tndrwang(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
Date: 2024-01-26 04:54:07
Message-ID: CAHewXNnaT6JM1wDR=ZxTiiRkgR+u_2Jd-AF-NiCCQVRL5ysX+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(at)paquier(dot)xyz> 于2024年1月26日周五 11:41写道：

> On Fri, Jan 26, 2024 at 11:33:24AM +0800, Tender Wang wrote:
> > How about using list *res replace int *res in getTokenTypes(), so we can
> > use list_append_unique().
> > In outer function, use list *tokens to replace int *tokens, and ntokens =
> > list_length(tokens) not list_length(stmt->tokentype).
>
> Yeah, I was wondering about this code path. If you feel strongly
> about that, would you like to write a patch?
>

Ok, I try to fix it.

> --
> Michael
>

--
Tender Wang
OpenPie: https://en.openpie.com/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tender Wang 2024-01-26 06:21:12 Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
Previous Message Tom Lane 2024-01-26 04:14:55 Re: BUG #18274: Error 'invalid XML content'