Re: Changing the result of ExecutorRun

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Changing the result of ExecutorRun
Date: 2008-10-31 17:14:31
Message-ID: 873aicheko.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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's PostgreSQL training!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Brad Nicholson 2008-10-31 17:23:23 Re: Enabling archive_mode without restart
Previous Message Tom Lane 2008-10-31 17:14:30 Re: Enabling archive_mode without restart