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

Re: Permission denied on fsync / Win32 (was right

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>
Cc: "<Magnus Hagander" <mha(at)sollentuna(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Permission denied on fsync / Win32 (was right
Date: 2006-04-14 00:41:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
"Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov> writes:
> The culprit is CLUSTER.  There is a batch file which runs CLUSTER
> against six, relatively small (60k rows between them) tables at 7am,
> 1pm, and 9pm.  Follows is the list of dates and hours when the
> "Permission denied" errors showed up.  They match up to a tee (although
> the error apparently sometimes persists for a while).

OK ... but what's still unclear is whether the failures are occurring
against the old relfilenode (the one just removed by the CLUSTER) or the
new one just added by CLUSTER.  If you note the relfilenodes assigned to
these tables just before and just after the next cycle of CLUSTERs, it
should be easy to tell what the complaints refer to.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Alexander KirpaDate: 2006-04-14 01:32:16
Subject: BUG #2394: Multiple TRUNCATE within transaction
Previous:From: Laurence DawsonDate: 2006-04-13 22:14:22
Subject: BUG #2393: update fails with unique constraint violation

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