Re: Updated ALTER TABLE ... SET TABLESPACE patch - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: Updated ALTER TABLE ... SET TABLESPACE patch
Date
Msg-id 200407120200.i6C20pB19670@candle.pha.pa.us
Whole thread Raw
In response to Re: Updated ALTER TABLE ... SET TABLESPACE patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
However, based on our feature freeze, maybe what we have now is fine and
I can just add the TODO item again.

---------------------------------------------------------------------------

Tom Lane wrote:
> Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> >> 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...
>
> I had forgotten that the original patch allowed that.  Personally I'd
> vote for taking it out, for the above-stated reasons --- any objections?
>
> If people do want to have it then we can instead change ALTER SET
> TABLESPACE to allow sequences; but we'd also need a nontrivial addition
> to pg_dump, so there had better be a better reason than "might be nice
> to have".
>
>             regards, tom lane
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Updated ALTER TABLE ... SET TABLESPACE patch
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Updated ALTER TABLE ... SET TABLESPACE patch