From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SET WITHOUT CLUSTER patch |
Date: | 2004-05-03 01:10:08 |
Message-ID: | 200405030110.i431A8A24747@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> On Sun, May 02, 2004 at 06:23:30PM -0400, Bruce Momjian wrote:
> > Christopher Kings-Lynne wrote:
> > > > Uh, if the CLUSTER doesn't recurse, the WITHOUT shouldn't either, I
> > > > think, and throwing an error seems fine to me, even if it isn't the same
> > > > wording as a syntax error.
> > >
> > > Well, maybe - up to you.
> >
> > Well, if we don't recurse on creation, does it make sense to recurse on
> > destruction? Seems it might surpise people. Do we have that asymetry
> > in any other area?
>
> I'm not sure if it's assymetric. You can't recursively set the cluster
> bit, because child tables may not have an equally named index. However
> when you are unsetting the bit it doesn't matter how is the index named.
Right, we can recurse on WITHOUT and not using WITH, but would people
expect WITHOUT to recurse?
If we allowed indexes to span tables, it would be nice for both to
recurse, but because we don't, I think neither should.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2004-05-03 01:41:22 | ANALYZE locks pg_listener in EXCLUSIVE for long time? |
Previous Message | Andrew Dunstan | 2004-05-03 00:49:14 | Re: Fixed directory locations in installs |