On 18 June 2010 16:37, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Andy Dale <andy.dale@xxxxxxxxx> writes:
> On 18 June 2010 16:06, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
>> You should be looking at pg_class.relfilenode, not OID. See
>> http://www.postgresql.org/docs/8.3/static/storage.html
> Ok, but when I have dumped the pg_class table into a file like so:> ...
> Grep-ing for the correct oid/filenode (110660 in my case), nothing isHm. You're sure you're looking at pg_class in the right database?
> returned.
If there really isn't a pg_class entry matching that relfilenode,
then the files are orphans and can be removed. There are some scenarios
where orphan files can be left behind, but they generally involve
database crashes ... have you had any of those?
regards, tom lane
To the best of my knowledge we have not had any DB crashes as yet. I am also replicating the DB using slony, could this be the cause of these weird orphans ? (it is neither of the sl_log_ tables)
