>> 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