From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: tablespace and sequences? |
Date: | 2004-08-18 01:23:30 |
Message-ID: | 4122AF92.6070103@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cygwin pgsql-hackers pgsql-hackers-win32 |
>>We decided it didn't make much sense to allow the on-row sequences to be
>>anywhere but the default tablespace.
>
>
> Hmmm...
>
> I can understand the performance/utility rationale, but I don't like the
> lack of orthogonality on principle. I like elegance;-) As a sequence looks
> a lot like a table, I guess it should not be that hard to have it anyway.
>
> Well, just my little opinion, and not a big issue.
>
> Thanks for your answer.
Well then, should you be able to move composite types to other
tablespaces as well??
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-08-18 01:33:53 | Re: tablespace and sequences? |
Previous Message | Fabien COELHO | 2004-08-17 16:17:52 | Re: tablespace and sequences? |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-08-18 01:33:53 | Re: tablespace and sequences? |
Previous Message | Christopher Kings-Lynne | 2004-08-18 01:18:25 | Re: psql's \l |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-08-18 01:33:53 | Re: tablespace and sequences? |
Previous Message | Fabien COELHO | 2004-08-17 16:17:52 | Re: tablespace and sequences? |