Skip site navigation (1) Skip section navigation (2)

Re: slow, long-running 'commit prepared'

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "John Smith" <sodgodofall(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: slow, long-running 'commit prepared'
Date: 2008-11-26 13:52:46
Message-ID: 7080.1227707566@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
"John Smith" <sodgodofall(at)gmail(dot)com> writes:
> 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?

It's impossible to say without knowing more about what the transaction
did.  But one piece of data you could check easily is the size of the
2PC state file (look into $PGDATA/pg_twophase/).

			regards, tom lane

In response to

Responses

pgsql-general by date

Next:From: Ivan Sergio BorgonovoDate: 2008-11-26 13:53:07
Subject: case when evaluating else condition anyway?
Previous:From: Alvaro HerreraDate: 2008-11-26 12:30:47
Subject: Re: Effect of stopped status collector process

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group