Re: Unable to determine what has a particular OID

From: Andy Dale <andy(dot)dale(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unable to determine what has a particular OID
Date: 2010-06-18 14:51:41
Message-ID: AANLkTincFvPgp4vJ1Ip0pIf7R4e78OiOJJSh4IOOK2PQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 18 June 2010 16:37, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Andy Dale <andy(dot)dale(at)gmail(dot)com> writes:
> > On 18 June 2010 16:06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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 is
> > returned.
>
> Hm. You're sure you're looking at pg_class in the right database?
>
> 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)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vick Khera 2010-06-18 14:59:31 Re: Excessive Deadlocks On Concurrent Inserts to Shared Parent Row
Previous Message Andy Dale 2010-06-18 14:46:34 Re: Unable to determine what has a particular OID