On Fri, Apr 8, 2011 at 4:51 PM, bricklen <brick...@gmail.com> wrote: > I've been noticing in my logs for the past few days the message you > note in the wiki. It seems to occur during a vacuum around 7:30am > every day. I will be running the suggested script shortly, but can > anyone tell me in how bad of shape my db is in? This is our production > db with two hot standby's running off it. > > grep -i 'could not access status of transaction' postgresql-2011-04*.log > postgresql-2011-04-06.log:2011-04-06 07:28:27 PDT [15882]: [1-1] > (user=postgres) (rhost=[local]) ERROR: could not access status of > transaction 1273385235 > postgresql-2011-04-07.log:2011-04-07 07:27:14 PDT [29790]: [1-1] > (user=postgres) (rhost=[local]) ERROR: could not access status of > transaction 1273385235 > postgresql-2011-04-08.log:2011-04-08 07:26:35 PDT [2402]: [1-1] > (user=postgres) (rhost=[local]) ERROR: could not access status of > transaction 1273385235
version 9.03, if that helps -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
