| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tablespace and sequences? |
| Date: | 2004-08-20 03:09:11 |
| Message-ID: | 15432.1092971351@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-cygwin pgsql-hackers pgsql-hackers-win32 |
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> At 12:37 PM 20/08/2004, Bruce Momjian wrote:
>> But that doesn't fix ascii dumps loaded via psql.
> It does; the ascii dump file is generated by exactly the same technique as
> pg_restore.
Right. Philip's suggestion would essentially use the same technique
that we previously adopted for portability of WITH/WITHOUT OIDS --- if
the "SET" fails, it won't stop the table from being created. (Note we
have to be careful that the semantics of the SET actually cause the
error to occur on the SET and not later on the CREATE. But that's
doable.)
It seemed like a reasonable idea to me...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2004-08-20 03:26:39 | Re: tablespace and sequences? |
| Previous Message | Philip Warner | 2004-08-20 02:47:44 | Re: tablespace and sequences? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2004-08-20 03:22:28 | Re: postgres uptime |
| Previous Message | Gavin Sherry | 2004-08-20 03:07:35 | Re: postgres uptime |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2004-08-20 03:26:39 | Re: tablespace and sequences? |
| Previous Message | Philip Warner | 2004-08-20 02:47:44 | Re: tablespace and sequences? |