From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Matthew Churcher <Matthew(dot)Churcher(at)realvnc(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Having trouble with pg_dumpall -o |
Date: | 2012-05-01 11:42:32 |
Message-ID: | CAA-aLv6m9GDcaz6RiRYVG11-Bs_XwusBH9WC9yb63EUm45CJ+A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1 May 2012 12:37, Matthew Churcher <Matthew(dot)Churcher(at)realvnc(dot)com> wrote:
> OK, I think I've worked out what's going on. I've got my wires crossed
> between table column OIDS (deprecated) and the OID which uniquely identifies
> each table (?always enabled?).
>
> We're not using OID for each column, only to reference the tables themselves
> as that's how triggers are referring to them.
>
> It appears the -o flag is for migrating table column oids which we're not
> using.
>
> So... any ideas how we can migrate the OID of the table itself? Or are we
> doing something we shouldn't?
You shouldn't be relying on OIDs as they're not really for the
end-user. Instead you should refer to objects by name. How are you
using them in triggers?
--
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Cole | 2012-05-01 11:47:33 | Re: PL/R install, no pgxs available |
Previous Message | Thom Brown | 2012-05-01 11:39:20 | Re: Having trouble with pg_dumpall -o |