Tom Lane a écrit :
Augustin Amann <[EMAIL PROTECTED]> writes:
Tom Lane a écrit :
What that really means is that the first process is waiting for a row
lock that's held by the second one --- that is, it's trying to update a
row that the second transaction has upd
Tom Lane a écrit :
Augustin Amann <[EMAIL PROTECTED]> writes:
During lock, we could see things like this in log file:
Process 5556 waits for ShareLock on transaction 14910066; blocked by
process 4940.
What that really means is that the first process is waiting for a row
lock
Hello,
Is a important number of update (no transaction, just one statement
after another) could result in ShareLock ?
I read the doc, but it's not clear to me.
There is a website (written with php, and using pg_connect), on two
loadbalanced Webserver, and one PostgreSQL database, on another s
