slow, long-running 'commit prepared' - Mailing list pgsql-general

From John Smith
Subject slow, long-running 'commit prepared'
Date
Msg-id b88f0d670811251917v535f75b2u1de558e25fad2cd9@mail.gmail.com
Whole thread Raw
Responses Re: slow, long-running 'commit prepared'  (Andrew Sullivan <ajs@crankycanuck.ca>)
Re: slow, long-running 'commit prepared'  ("John Smith" <sodgodofall@gmail.com>)
Re: slow, long-running 'commit prepared'  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I have a pg instance with 700GB of data, almost all of which is in one
table. When I PREPARE and then COMMIT PREPARED a transaction that
reads & writes to a large fraction of that data (about 10%,
effectively randomly chosen rows and so every file in the table is
modified), the COMMIT PREPARED sometimes takes a very long time--2 to
5 minutes. Is this expected? Is it possible for the commit to hang
waiting on some lock for this long? I haven't yet been able to examine
pg_locks during this 5 minute delay. There is very little
concurrency--only a couple of open sessions--when the COMMIT PREPARED
is issued.

Thanks for your help,
John

pgsql-general by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Re: Effect of stopped status collector process
Next
From: Andrew Sullivan
Date:
Subject: Re: slow, long-running 'commit prepared'