Re: introduce "default_use_oids"

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Neil Conway <neilc(at)samurai(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: introduce "default_use_oids"
Date: 2003-12-02 06:56:37
Message-ID: 3FCC37A5.6090906@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> Significant effort has been invested to make pg_dump output portable, and
> I've not had any problems with it last time I tried it. Please explain
> why you think it's "totally" non-portable.

Functions, indexes, operators, types, aggregates, users, groups,
databases, inheritance, clustering, col stats, col storage, ...

What IS compatible? Very basic table definitions?

Chris

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Manfred Koizar 2003-12-02 09:24:30 Re: [HACKERS] Index creation takes for ever
Previous Message Christopher Kings-Lynne 2003-12-02 06:52:01 Re: YA Cygwin DLLIMPORT patch