| From: | Francisco J Reyes <fran(at)natserv(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Christoph Dalitz <christoph(dot)dalitz(at)hs-niederrhein(dot)de>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PG Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Status of tablespaces |
| Date: | 2003-01-29 15:32:56 |
| Message-ID: | 20030129103144.H80386-100000@zoraida.natserv.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 28 Jan 2003, Tom Lane wrote:
> Francisco J Reyes <fran(at)natserv(dot)net> writes:
> > I also wonder if the syntax of the current create DB won't have to be
> > changed once tablespaces are created.
>
> I'd be inclined to remove the WITH LOCATION option the instant we have
> an adequate tablespace substitute. It's such an ugly, messy, unsafe
> way to do things --- depending on environment variables is bad news.
> There are things I'm willing to keep around in the name of backward
> compatibility, but this isn't one of them.
How about putting a warning on the docs that this functionality may be
removed once Tablespaces are implemented.
One commonly doesn't go around creating tables every day, but for those
considering this function may be good to warn then in advance.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KK | 2003-01-29 15:43:56 | Re: Firewalls and Postgres |
| Previous Message | Richard Huxton | 2003-01-29 15:30:51 | Re: ERROR: language "plpgsql" does not exist |