Re: Updated ALTER TABLE ... SET TABLESPACE patch

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Updated ALTER TABLE ... SET TABLESPACE patch
Date: 2004-07-12 01:32:23
Message-ID: 40F1EA27.40501@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> Please remove that; if I thought either one was a good idea, I would
> have allowed it in the committed patch.
>
> Sequences are too small to be worth moving around, and may someday be
> reimplemented in a fashion that doesn't use up a separate disk file for
> each one. If we allow SET TABLESPACE on them we will be limiting our
> future flexibility for no useful gain.

Why do we allow them to be created in tablespaces in the first place
then? Seems like a bit of a misfeature? I mean we don't allow views in
tablespaces...

Chris

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2004-07-12 01:32:57 Re: Updated ALTER TABLE ... SET TABLESPACE patch
Previous Message Bruce Momjian 2004-07-12 01:22:56 Re: Docs additions: tablespace examples