| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, 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 12:48:49 |
| Message-ID: | 200312021248.hB2Cmnw16486@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Peter Eisentraut wrote:
> Neil Conway writes:
>
> > I'm really not sure we do: the SQL produced by pg_dump was totally
> > non-portable before,
>
> 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.
Also, I think we have to have a SET before every CREATE TABLE. If we
don't how does it work if we restore a single table from the dump? We
must handle this type of thing with SET SESSION AUTHORIZATION to make
sure we are the proper owner, so it seems we could do the same with
oids.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-12-02 15:09:43 | Re: introduce "default_use_oids" |
| Previous Message | Bruce Momjian | 2003-12-02 12:39:56 | Re: YA Cygwin DLLIMPORT patch |