Re: Returning from a rule with extended query protocol

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Rychlewski <greg(dot)rychlewski(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Returning from a rule with extended query protocol
Date: 2024-08-12 21:26:02
Message-ID: CAGECzQQLbceEy==tXAXG2nSy4OfK8C_rbfzb9K+ToYzM0MdaQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 11 Aug 2024 at 23:54, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I think this might be the same issue recently discussed here:
>
> https://www.postgresql.org/message-id/flat/1df84daa-7d0d-e8cc-4762-85523e45e5e7%40mailbox.org

Yeah that's definitely the same issue.

> That discussion was leaning towards the idea that the cost-benefit
> of fixing this isn't attractive and we should just document the
> discrepancy. However, with two reports now, maybe we should rethink.

I think it's interesting that both reports use rules in the same way,
i.e. to implement soft-deletes. That indeed seems like a pretty good
usecase for them. And since pretty much every serious client library
uses the extended query protocol, this breaks that usecase. But if
it's hard to fix, I'm indeed not sure if it's worth the effort. If we
don't we should definitely document it though, at CREATE RULE and in
the protocol spec.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2024-08-12 21:30:32 Re: format_datum debugging function
Previous Message Alexander Korotkov 2024-08-12 21:25:47 Re: [HACKERS] make async slave to wait for lsn to be replayed