Re: Changing the result of ExecutorRun - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Changing the result of ExecutorRun
Date
Msg-id 873aicheko.fsf@oxford.xeocode.com
Whole thread Raw
In response to Changing the result of ExecutorRun  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Changing the result of ExecutorRun
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> * Return the count of tuples processed, probably as a long since that's
> what the input limit-count is.  There are potential overflow issues with
> this definition on 32-bit machines, though that's not going to affect
> functions.c since it passes a limit of 1 tuple in the cases where it
> needs to examine the result, and no one else presently cares at all.
> But the possibility of overflow might limit the usefulness of this
> definition in other scenarios.

And what would that mean for a cursor which was read forward and backward?

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about
EnterpriseDB'sPostgreSQL training!
 


pgsql-hackers by date:

Previous
From: "Hitoshi Harada"
Date:
Subject: Re: Window Functions: patch for CommitFest:Nov.
Next
From: Tom Lane
Date:
Subject: Re: Enabling archive_mode without restart