suggestions in the test environment.
Thank you,
Dmitry
From: Jeff Janes
Sent: Monday, June 19, 2017 1:16 PM
To: Dmitry O Litvintsev
Cc: Andreas Kretschmer; pgsql-general@postgresql.org
Subject: Re: [GENERAL] autovacuum holds exclusive lock on table
hmer
Sent: Tuesday, June 13, 2017 1:54 PM
To: pgsql-general@postgresql.org; Dmitry O Litvintsev;
pgsql-general@postgresql.org
Subject: Re: [GENERAL] autovacuum holds exclusive lock on table preventing it
from to be updated
Am 13. Juni 2017 20:04:04 MESZ schrieb Dmitry O Litvintsev :
>
&
Hi,
I run postgresql 9.3.17. I am preparing for a major database schema upgrade.
I copied production database to test system using pg_basebackup.
Having started the database and waited for all WALs to be applied I proceeded
to run
schema modifications.
Immediately I run into issue - updat
: Wednesday, February 18, 2015 6:19 AM
To: Dmitry O Litvintsev
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgresql93-9.3.5: deadlock when updating parent table
expected?
Dmitry O Litvintsev wrote:
> Hi,
>
> I recently updated to postgresql93-9.3.5 (from 9.2.9). I see frequent
&g
Thank you, Bill,
Yes, deadlock occurs when there are multiple processes insert
concurrently into file table with the same volume id field.
I used "sometimes" as opposed to "all the time".
I think you advise to retry transaction or add select for update prior
to insert. I will pursue this (to
Hi,
I recently updated to postgresql93-9.3.5 (from 9.2.9). I see frequent deadlocks
when updating parent table in insert into child table. There is foreign key
constraint between
child table and parent table. Parent table is updated on by trigger in insert
into child table. So
pretty much st