Re: FOR PORTION OF should not allow WHERE CURRENT OF

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: FOR PORTION OF should not allow WHERE CURRENT OF
Date: 2026-06-29 13:27:18
Message-ID: 07843c16-3bb9-4156-86cd-bebf7bd0c863@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 17.06.26 07:10, Paul A Jungwirth wrote:
> I found a bug with FOR PORTION OF: you shouldn't be able to provide it
> while using WHERE CURRENT OF with a cursor, but you can. (And it
> doesn't do anything sensible.)
>
> According to the SQL standard, combining these is not allowed: you can
> give FOR PORTION OF with an <update/delete statement: searched> but
> not an <update/delete statement: positioned>. I've attached a patch to
> raise an error if you try to use both.

committed

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-06-29 13:38:08 Re: coerce_type discard unnecessary CollateExprs
Previous Message Thomas Munro 2026-06-29 13:19:29 Per-thread leak in ECPG's memory.c