Re: pg crash shortly after 9.1.1 -> 9.1.2 upgrade

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joseph Shraibman <jks(at)selectacast(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg crash shortly after 9.1.1 -> 9.1.2 upgrade
Date: 2011-12-08 05:54:25
Message-ID: 14426.1323323665@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Joseph Shraibman <jks(at)selectacast(dot)net> writes:
> All was fine until:
> LOG: statement: select "_devel".cleanupEvent('10 minutes'::interval,
> 'false'::boolean);
> ERROR: could not open file "base/16406/2072097_fsm": Permission denied

That's pretty weird. What were the permissions on that file? Was it
properly owned by the postgres user?

> WARNING: AbortTransaction while in COMMIT state
> PANIC: cannot abort transaction 7108311, it was already committed

And that's even weirder, since it implies that we tried to open the FSM
file during post-commit cleanup. The commit-record printout suggests
that we probably were trying to delete the file due to a committed DROP
TABLE operation, but I don't understand why we tried to open the file
rather than just unlink it.

Can you reproduce this? Can you show us what cleanupEvent() does?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mamatha_Kagathi_Chan 2011-12-08 06:10:14 Re: [pgadmin-support] Help for Migration
Previous Message Richard Weiss 2011-12-08 05:28:38 Very slow table