Re: BUG #2712: could not fsync segment: Permission

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas H(dot)" <me(at)alternize(dot)com>
Cc: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org, "Magnus Hagander" <mha(at)sollentuna(dot)net>
Subject: Re: BUG #2712: could not fsync segment: Permission
Date: 2006-10-23 20:59:22
Message-ID: 28539.1161637162@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

"Thomas H." <me(at)alternize(dot)com> writes:
> with process explorer i can actually check which postgres.exe instance (in
> all cases i've checked its just 1 instance, and always just 1 file) holds
> the lock for the file in question.

So which one is it?

> the postgres instance that holds the lock eventually closes the filehandle
> after some minutes. the process itself is not killed but continues
> thereafter.

That sounds a bit like what I'd expect the bgwriter to do, but the
bgwriter is also the one trying to issue the fsync.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas H. 2006-10-23 21:08:07 Re: BUG #2712: could not fsync segment: Permission
Previous Message Thomas H. 2006-10-23 20:49:37 Re: BUG #2712: could not fsync segment: Permission

Browse pgsql-patches by date

  From Date Subject
Next Message Thomas H. 2006-10-23 21:08:07 Re: BUG #2712: could not fsync segment: Permission
Previous Message Tom Lane 2006-10-23 20:57:32 Re: COPY does not work with regproc and aclitem