| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Greg Rychlewski <greg(dot)rychlewski(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Returning from a rule with extended query protocol |
| Date: | 2024-08-11 20:15:41 |
| Message-ID: | CAGECzQTLP+c9cOwEoBzHcyP3v9AfjLLThKw+PpTXN+hk=NcVuQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 11 Aug 2024 at 13:29, Greg Rychlewski <greg(dot)rychlewski(at)gmail(dot)com> wrote:
> I was testing creating a rule that uses RETURNING and noticed a difference between the extended query protocol and the simple query protocol. In the former, RETURNING is ignored (at least in my case) and the latter it is respected:
That seems like a bug to me. The simple and extended protocol should
return the same data for the same query. I'm guessing CREATE RULE
isn't often enough for this difference to be noticed earlier. So yeah
please dig through the code and submit a patch to fix this.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-08-11 21:54:25 | Re: Returning from a rule with extended query protocol |
| Previous Message | Joel Jacobson | 2024-08-11 20:04:26 | Re: Optimize mul_var() for var1ndigits >= 8 |