Re: [BUGS] BUG #6061: Progresql.exe memory usage using HOLD cursor.

2011-06-16 Thread Delorme, Yann
@postgresql.org Objet : Re: [BUGS] BUG #6061: Progresql.exe memory usage using HOLD cursor. Yann yann.delo...@esker.fr writes: The issue is that in this case all rows are store in memory instead of file in the process postgresql.exe I think the issue is in the file tuplestore.c. When a tuple is added

Re: [BUGS] BUG #6061: Progresql.exe memory usage using HOLD cursor.

2011-06-16 Thread Guillaume Smet
Yann, 2011/6/16 Delorme, Yann yann.delo...@esker.fr: Thanks Do you think that it will be fix in future release 9.1 ? Tom commited a fix in all the supported releases where the bug is present including 9.0:

[BUGS] BUG #6061: Progresql.exe memory usage using HOLD cursor.

2011-06-15 Thread Yann
The following bug has been logged online: Bug reference: 6061 Logged by: Yann Email address: yann.delo...@esker.fr PostgreSQL version: 9.0.4 Operating system: Windows 2008 R2 Description:Progresql.exe memory usage using HOLD cursor. Details: Hello, I use

Re: [BUGS] BUG #6061: Progresql.exe memory usage using HOLD cursor.

2011-06-15 Thread Tom Lane
Yann yann.delo...@esker.fr writes: The issue is that in this case all rows are store in memory instead of file in the process postgresql.exe I think the issue is in the file tuplestore.c. When a tuple is added the function static void tuplestore_puttuple_common(Tuplestorestate *state, void