Table OIDs are fixed values?

From: valeriof <valerio_farruggio(at)hotmail(dot)com>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: Table OIDs are fixed values?
Date: 2017-05-10 09:52:02
Message-ID: 1494409922149-5960746.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-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.

Browse pgadmin-hackers by date

  From Date Subject
Next Message Sarah McAlear 2017-05-10 13:37:21 Re: [patch] Dependents and Dependencies in GreenPlum
Previous Message Devrim Gündüz 2017-05-10 09:32:19 Re: Install of pgadmin4 from package fails ...