| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, David Fetter <david(at)fetter(dot)org>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PGXS: REGRESS_OPTS=--load-language=plpgsql |
| Date: | 2010-02-20 23:57:02 |
| Message-ID: | 24475.1266710222@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> Just throwing this out there: would a syntax such as CREATE OF NOT
> EXISTS, a complement to DROP IF EXISTS, avoid the permissions issue?
No, it'd just move it to a different place: now you risk breaking
the restored state rather than pre-existing state.
> And if so, would that be a syntax we'd want to accept in general?
> Could the be a CREATE IF NOT EXISTS TABLE?
*Please* go read some of the linked older discussions before you propose
that. I don't want to rehash it yet again.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-02-20 23:58:52 | Re: alpha4 bundled -- please verify |
| Previous Message | Lucas | 2010-02-20 23:55:56 | Re: scheduler in core |