Bjørn T Johansen wrote:
I am trying to change the password for the postgres user but it doesn't work...
I
have tried changing it from pgAdmin, EMS PostgreSQL Manager, etc but whatever
password I set, I still can log in without using password (And it seems
that no
sql code is run on the ser
I'd use pg_dump anyway - unless you have hundreds of databases, it makes
it easier to keep by backups separate.
I will do that then. Thanks.
Here is the script I use for my daily backups nothing special but it
works well. Just run it as a user with admin privs on the database. It
will pull
If the deadlocks occur because different transactions actually try to
update the same rows concurrently, then this is an appropriate solution.
However I wonder if Gavin is getting bitten by foreign key deadlocks.
Is there any foreign key reference from the stats table to other tables?
Tom,
The
ents by id inside a transaction, and
the deadlocks should go away.
HTH,
Csaba.
On Wed, 2005-06-15 at 13:10, Gavin Love wrote:
I am getting a number of deadlock errors in my log files and I was
wondering if anyone knows how I can stop them.
Query failed: ERROR: deadlock detected DETAIL: Process
I am getting a number of deadlock errors in my log files and I was
wondering if anyone knows how I can stop them.
Query failed: ERROR: deadlock detected DETAIL: Process 11931 waits for
ShareLock on transaction 148236867; blocked by process 11932. Process
11932 waits for ShareLock on transact