| From: | Andrew - Supernews <andrew+nonews(at)supernews(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SPI bug. |
| Date: | 2005-05-01 12:40:19 |
| Message-ID: | slrnd79jhj.2da6.andrew+nonews@trinity.supernews.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2005-05-01, Neil Conway <neilc(at)samurai(dot)com> wrote:
> Tzahi Fadida wrote:
>> I think the solution can be either changing the FETCH_ALL to
>> INT_MAX or changing the interface parameter count and subsequent usages
>> to long.
>
> I think changing SPI_cursor_fetch() and SPI_cursor_move() to take a
> "long" for the "count" parameter is the right fix for HEAD. It would
> probably not be wise to backport, though, as it is probably not worth
> breaking ABI compatibility for SPI during a stable release series.
While you're at it, how about a way to specify WITH SCROLL for a cursor
created in SPI? At the moment, SPI_cursor_open hardwires the scroll option
according to the result of ExecSupportsBackwardScan.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Hallgren | 2005-05-01 13:49:19 | Re: SPI bug. |
| Previous Message | adnandursun | 2005-05-01 12:09:37 | Re: Feature freeze date for 8.1 |