| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: tablespace and sequences? |
| Date: | 2004-08-17 15:30:03 |
| Message-ID: | Pine.LNX.4.58.0408171722300.30419@sablons.cri.ensmp.fr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-cygwin pgsql-hackers pgsql-hackers-win32 |
Dear Bruce,
> > (1) the "CREATE SEQUENCE foo TABLESPACE disk2" syntax does not seem
> > to be implemented.
> >
> > (2) when creating an implicit sequence with SERIAL, the sequence
> > is created in the tablespace of the schema/database, not the one
> > of the table, although indexes are added to the tablespace
> > of the table. It would seem more logical to put it in
> > the same table space as the table by default?
>
> 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.
--
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-08-17 15:35:02 | Re: tablespace and sequences? |
| Previous Message | Bruce Momjian | 2004-08-17 15:17:26 | Re: tablespace and sequences? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-08-17 15:35:02 | Re: tablespace and sequences? |
| Previous Message | Oliver Jowett | 2004-08-17 15:18:40 | LDFLAGS vs. shared libraries |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Kmetec | 2004-08-17 15:34:21 | Re: Win32 PostgreSQL 8.0 Beta 1 Installer available |
| Previous Message | Tom Lane | 2004-08-17 15:18:29 | Re: [PATCHES] GUC variables invisible to contrib/ modules |