MIME-Version: 1.0
References: <CAHYXj6eJiX0jQpq4u7xYc1qy3=zBN+sPhGMTJETAF0fdoSyNUA@mail.gmail.com>
 <CAKAnmmJfKZejX0yE8dMHRZiQApq-PO_+aetGCHkkjK3VdOjD3w@mail.gmail.com>
 <CAHYXj6etiV1pTBvBiQFZ=jqxvNHczZio9cSSb7gMy+RrWwZTTQ@mail.gmail.com> <1568BE1C-261C-474A-803F-66B8B757F1B1@gmail.com>
In-Reply-To: <1568BE1C-261C-474A-803F-66B8B757F1B1@gmail.com>
From: Jacob Biesinger <jake.biesinger@gmail.com>
Date: Wed, 28 Aug 2024 15:19:54 -0700
Message-ID: <CAHYXj6dTw4Xz8_ud3DqsJn8JiJNC9a9sazs7bsj1_=AvjgNhQA@mail.gmail.com>
Subject: Re: Ghost data from failed FDW transactions?
To: Rob Sargent <robjsargent@gmail.com>
Cc: Greg Sabino Mullane <htamfids@gmail.com>, pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000009dd9280620c5c23c"
Archived-At: <https://www.postgresql.org/message-id/CAHYXj6dTw4Xz8_ud3DqsJn8JiJNC9a9sazs7bsj1_%3DAvjgNhQA%40mail.gmail.com>
Precedence: bulk

--0000000000009dd9280620c5c23c
Content-Type: text/plain; charset="UTF-8"

>
> Any value in supplying a single insert statement a la (less back and forth
> perhaps?):
>

Yes, absolutely that would be better. This particular endpoint has some
ancient + crufty code backing it (migrated from a NoSQL DB with a
db-agnostic shim that we're slowly replacing). The old code likes doing
things client-side instead of being sane about SQL semantics.

But I don't think that would affect the issue here, right?

--
Jake Biesinger

--0000000000009dd9280620c5c23c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div style=3D"overflow-wrap: break-word;">Any value in s=
upplying a single insert statement a la (less back and forth perhaps?):</di=
v></blockquote><div><br></div><div>Yes, absolutely that would be better. Th=
is particular endpoint has some ancient=C2=A0+ crufty code backing it (migr=
ated from a NoSQL DB with a db-agnostic shim that we&#39;re slowly replacin=
g). The old code likes doing things client-side instead of being sane about=
 SQL semantics.</div><div><br></div><div>But I don&#39;t think that would a=
ffect the issue here, right?</div><div><br></div>--<br>Jake Biesinger<br><d=
iv>=C2=A0</div></div></div>

--0000000000009dd9280620c5c23c--