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? Thanks, Matt. -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Thom Brown Sent: 01 May 2012 11:58 To: Matthew Churcher Cc: pgsql-general@xxxxxxxxxxxxxx Subject: Re: Having trouble with pg_dumpall -o On 1 May 2012 11:55, Matthew Churcher <Matthew.Churcher@xxxxxxxxxxx> wrote: > Thanks Thom, that's really useful to know however I've been unable to > get it working with pg_dump either. Are you able to offer any insight there? > What command line options are you using? > > I get the same result with: > pg_dump -o mydatabase > pg_dump mydatabase Can you confirm your tables actually use OIDs? By default they don't. -- Thom -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
