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

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

From: "Thomas H(dot)" <me(at)alternize(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 21:08:07
Message-ID: 02bb01c6f6e7$572998e0$0201a8c0@iwing (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-patches
>> 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?

it's always one of the db-"slaves" and not "logger process", "stats 
collector process" or "writer process":

right now its PID 4844 ("\BaseNamedObjects\pgident: postgres: db_outnow 
outnow1 127.0.0.1(2122) idle") that tries to write 
"D:\DB\PostgreSQL-8.2\data\base\3964774\6422331"

can i somehow check what object that file-OID belong(ed/s) to?

- thomas 



In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-10-23 21:21:15
Subject: Re: BUG #2712: could not fsync segment: Permission
Previous:From: Tom LaneDate: 2006-10-23 20:59:22
Subject: Re: BUG #2712: could not fsync segment: Permission

pgsql-patches by date

Next:From: Tom LaneDate: 2006-10-23 21:21:15
Subject: Re: BUG #2712: could not fsync segment: Permission
Previous:From: Tom LaneDate: 2006-10-23 20:59:22
Subject: Re: BUG #2712: could not fsync segment: Permission

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