From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Josh Tolley" <eggyknap(at)gmail(dot)com> |
Cc: | "S Sharma" <data_arch(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Feature Request - Defining default table space for Indexes in Conf file |
Date: | 2007-10-03 18:40:12 |
Message-ID: | 29610.1191436812@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Josh Tolley" <eggyknap(at)gmail(dot)com> writes:
> On 10/1/07, S Sharma <data_arch(at)yahoo(dot)com> wrote:
>> It would be nice to have a feature to define a default table space for
>> indexes in db conf file and all indexed are created in that table space.
> Although the most basic optimization suggested when using tablespaces
> is always "Put indexes on one and data on another to avoid disk
> contention", I doubt that the ideal optimization for many workloads,
> which means sticking such a thing in a config file might not be such a
> good idea. In other words, a DBA probably ought to think harder about
> optimizing his/her use of tablespaces than just "I'll put indexes on
> this one and data on another".
Yeah, I think that argument is why we did not provide such a setup to
begin with...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2007-10-03 18:46:40 | Re: PITR Recovery and out-of-sync indexes |
Previous Message | Tom Lane | 2007-10-03 18:38:36 | Re: PITR and Compressed WALS |