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 21:21:15
Message-ID: 28745.1161638475@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:
> 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"

Do you actually mean it's trying to write that file? Or is it just
sitting there holding the open filehandle?

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

You can check in pg_class.relfilenode and pg_class.oid of that database
to see if you get a match. But our theory is that this table has been
deleted ...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-10-23 21:44:12 global symbol conflict in test/pgtypeslib/dt_test2.pgc
Previous Message Thomas H. 2006-10-23 21:08:07 Re: BUG #2712: could not fsync segment: Permission

Browse pgsql-patches by date

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