From: | "Rosny" <sehatrosny(at)hotmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: TableSpace Design issues on Postgres 8.0 beta 5 |
Date: | 2004-12-07 07:58:06 |
Message-ID: | cp3nqc$27fl$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Thanks for the response.
I just start to get a feel of where TableSpace will be used. You are right I
do not have 7000 logical filesystems.
I am assuming using TableSpace as organization of files in folders in
Windows 2003 Environment. So, each
TableSpace will represent one folder(directory) in a drive. But this doesnot
work to well for my design.
Since pgAdmin III GUI take 2 hours just to load approximately 14000 tables.
I am not using TableSpace approach anymore. I am using multiple database
approach.
Anyway, thanks for the response. Today testing by taking several option to
the limit. I kind of having some ideas
for future scability.
Rosny
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in message
news:10164(dot)1102394676(at)sss(dot)pgh(dot)pa(dot)us(dot)(dot)(dot)
> "Rosny" <sehatrosny(at)hotmail(dot)com> writes:
> > B. For each department create tablespace. (Which means, if there
> > are 7000 departments, there will be 7000 tablespace each contains
> > 20 tables).
>
> If your system has seven thousand separate logical filesystems attached
> to it, there might be some value in having seven thousand tablespaces.
> But I will bet a great deal that it does not and there isn't.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2004-12-07 08:03:08 | Re: Config review |
Previous Message | Tom Lane | 2004-12-07 05:03:56 | Re: Config Check |