On 2011-01-27, Girts Laudaks wrote:
> Hi,
>
> What could be the possible damage if a database is migraged without the
> -o (OID) option? Integrity of data?
some things that used OID might fail to work.
Postgres doesn't need them, does your application?
> What are the options to solve this probl
On Friday 28 January 2011 4:54:18 am Girts Laudaks wrote:
> Well, seems that everything is OK. There are no OIDs used from the
> application side but they still appear in the database tables, this was
> what made the confusion.
>
> Thanks,
> G.
>
OIDS on user tables have not been on by default sin
Well, seems that everything is OK. There are no OIDs used from the
application side but they still appear in the database tables, this was
what made the confusion.
Thanks,
G.
On 2011.01.27. 21:33, Adrian Klaver wrote:
On 01/27/2011 04:52 AM, Girts Laudaks wrote:
Hi,
What could be the possib
On 01/27/2011 04:52 AM, Girts Laudaks wrote:
Hi,
What could be the possible damage if a database is migraged without the
-o (OID) option? Integrity of data?
User OIDs are deprecated,so the main problem is whether you are
currently using them as foreign keys. If you do not specify the -o
swit
Hi,
What could be the possible damage if a database is migraged without the
-o (OID) option? Integrity of data?
What are the options to solve this problem if it is migrated this way?
Shouldn't pg_dumpall work like an exact copy of db?
What could have gone wrong if only these commands were used?
