From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | "fkater(at)googlemail(dot)com" <fkater(at)googlemail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Alternative to tableoids? |
Date: | 2008-02-04 20:11:24 |
Message-ID: | 47A7716C.4040205@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
fkater(at)googlemail(dot)com wrote:
> Hi,
>
> what's an alternative to tableoids?
>
> As I've learned today they are not consistant across pg_dump/restore.
>
> I need to point to (lots of dynamically added) tables and used tableoids
> before.
>
> Are there other solutions to point to tables besides using tableoids
> or wasting disk space using the strings of 'schema' and 'tablename'
> everywhere as a reference?
Are you seriously saying that you have so many tables that storing their
names is a problem?
Anyway, since your code is expecting something that looks like an OID,
why not just build your own, something like:
CREATE TABLE my_sys_object_tracker (
objoid SERIAL,
objschema name NOT NULL,
objname name NOT NULL,
PRIMARY KEY (objoid),
CONSTRAINT unique_obj_name UNIQUE (objschema, objname)
);
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2008-02-04 20:14:24 | Re: [GENERAL] PostgreSQL Certification -- wind it up, please. |
Previous Message | Erik Jones | 2008-02-04 20:03:39 | Re: Out of Memory errors while running pg_dump |