Re: Changing the result of ExecutorRun
| От | Gregory Stark |
|---|---|
| Тема | Re: Changing the result of ExecutorRun |
| Дата | |
| Msg-id | 873aicheko.fsf@oxford.xeocode.com обсуждение исходный текст |
| Ответ на | Changing the result of ExecutorRun (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Changing the result of ExecutorRun
|
| Список | 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 по дате отправления: