Re: [BUGS] transactions getting slon in councurrent environment

2006-12-29 Thread Russell Smith
Tigran Mkrtchyan wrote: Does it mean that I have to commit after each select statement? Here what the manual says: Description COMMIT commits the current transaction. All changes made by the transaction become visible to others and are guaranteed to be durable if a crash occurs.

Re: [BUGS] transactions getting slon in councurrent environment

2006-12-29 Thread Tigran Mkrtchyan
Does it mean that I have to commit after each select statement? Here what the manual says: Description COMMIT commits the current transaction. All changes made by the transaction become visible to others and are guaranteed to be durable if a crash occurs. --- Does select

Re: [BUGS] transactions getting slon in councurrent environment

2006-12-28 Thread Tom Lane
Tigran Mkrtchyan <[EMAIL PROTECTED]> writes: > I got a incorrect or unexpected behavior in concurrent environment. This is not a bug, nor even surprising. Since you haven't committed the second transaction, there are a growing number of dead-but-not-recyclable versions of the updated row. The ac