Server-side memory leak in PostgreSQL

[soci]

Server-side memory leak in PostgreSQL

[mloskot]

Can you confirm use are using prepared statements?
Recently, fix for prepared statement leak has been applied (see 02bb841b).

Unfortunately, the fix is causing regression. You can take a look at detailed explanation posted in the issue #13
I haven't had chance to come up with solution of this problem yet.

[b-s-a]

yes. I have use prepared statements (for rowset only).

[mloskot]

And, can you confirm you have tried the source code with the fix for prepared statement leak applied. Namely, are you using SOCI with 02bb841b changes?

[b-s-a]

Yes. I confirm. I have use TODAY master. And I in real-time see (top), that postgres process eats 100KB per second (I do prepare every second).

[b-s-a]

I use prepare only in this construction:
{
soci::rowsetsoci::row res = (db.prepare << ....);
for(soci::rowsetsoci::row::iterator it = res.begin(), end = res.end(); it != end; ++it)
....
}

[mloskot]

The fix has been merged into master SHA1: 8c05035
It also seems to solve the problem reported in the issue #13, great!
So, I'm going to partially revert the SHA1: 02bb841 fix, to avoid Premature deallocation of prepared statement. The SHA1: 8c05035 fix should be sufficient for that scenario too.

Thank you!