public inbox for [email protected]  

help / color / mirror / Atom feed

From: valeriof <[email protected]>
To: [email protected]
Subject: Table OIDs are fixed values?
Date: Wed, 10 May 2017 02:52:02 -0700 (MST)
Message-ID: <[email protected]> (raw)
List-Unsubscribe:  <mailto:[email protected]?body=unsub%20pgadmin-hackers>

Hi,
I'm building an application that needs to internally store a table ID for
each of the tables that have been loaded into it. I found that the pg_class
catalog table contains the oid column that is an unique identifier for each
table. NOTICE that I'm not talking about the oid metacolumn that can be used
optionally in any custom table as a replacement of a primary key; here it's
just a fixed table identifier that we need.

The question is, it appears that the table oids after some time, are changed
internally and the old values do not match anymore with the current ones.
The application needs the actual oids as it has to run a Postgres  plugin
where internally checks for the table id to make sure it is handling a table
loaded into the application.

What kind of events can trigger the oid change? Is there any other internal
ID that can be used for this purpose?

Thanks,
Valerio



--
View this message in context: http://www.postgresql-archive.org/Table-OIDs-are-fixed-values-tp5960746.html
Sent from the PostgreSQL - pgadmin hackers mailing list archive at Nabble.com.


-- 
Sent via pgadmin-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: Table OIDs are fixed values?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox