On Tue, Dec 27, 2011 at 12:47 PM, Tom Lane wrote:
> wcting...@163.com writes:
>> The reason is that the function p_test_execute is executed twice, when
>> *fetch*, it is first executed, and when transaction commit, because the
>> cursor is a *holdable* cursor, it is executed again.
>
> Yup. I don
At 2011-12-28 01:47:20,"Tom Lane" t...@sss.pgh.pa.us> wrote:
Yup. I don't particularly see this as a bug. If you were to manually
>rewind and rescan the cursor (ie, MOVE BACKWARD ALL and re-fetch),
>the function would be executed multiple times too. If you don't want
>that to happen, the best wa
wcting...@163.com writes:
> The reason is that the function p_test_execute is executed twice, when
> *fetch*, it is first executed, and when transaction commit, because the
> cursor is a *holdable* cursor, it is executed again.
Yup. I don't particularly see this as a bug. If you were to manually
The following bug has been logged on the website:
Bug reference: 6360
Logged by: ctwang
Email address: wcting...@163.com
PostgreSQL version: 9.0.5
Operating system: linux 2.6.18-128.7AXS3
Description:
create table test_execute(id int,name varchar(40));
insert into te
