default_index_tablespace?
PostgreSQL 8.0 brought a great tablespaces feature. However, it's still
a real pain for one who wants to separate tables and indices to different
tablespaces: he has to do it manually, explicitely specifying tablespace
for each index.
Thus, I think it would be handy to have "default_index_tablespace" server
variable. Any thoughts?
--
Fduch M. Pravking
Yeah, I could use that too :)
I think that would be good in order to separate users on different disks
easily (if this parameter could be set by user too ...)
Le Jeudi 01 Décembre 2005 08:32, Alexander M. Pravking a écrit :
Show quoted text
PostgreSQL 8.0 brought a great tablespaces feature. However, it's still
a real pain for one who wants to separate tables and indices to different
tablespaces: he has to do it manually, explicitely specifying tablespace
for each index.Thus, I think it would be handy to have "default_index_tablespace" server
variable. Any thoughts?
On 12/1/05, Alexander M. Pravking <fduch@antar.bryansk.ru> wrote:
PostgreSQL 8.0 brought a great tablespaces feature. However, it's still
a real pain for one who wants to separate tables and indices to different
tablespaces: he has to do it manually, explicitely specifying tablespace
for each index.Thus, I think it would be handy to have "default_index_tablespace" server
variable. Any thoughts?
We would use such a thing. Our databases use three partitions: log, data,
index. We currently create our databases like:
CREATE DATABASE dbname OWNER owner TABLESPACE tsname;
We then specify another index tablespace on index creation (which really
isn't that difficult).
Adding an INDEX_TABLESPACE option to CREATE DATABASE might be worthwhile if
what we have done is typical. Or if pg maintainers want to suggest this
usage as sensible.
-K
TODO?
%Add default_index_tablespace GUC and database parameter.
On Thu, Dec 01, 2005 at 11:48:28AM -0600, Kelly Burkhart wrote:
On 12/1/05, Alexander M. Pravking <fduch@antar.bryansk.ru> wrote:
PostgreSQL 8.0 brought a great tablespaces feature. However, it's still
a real pain for one who wants to separate tables and indices to different
tablespaces: he has to do it manually, explicitely specifying tablespace
for each index.Thus, I think it would be handy to have "default_index_tablespace" server
variable. Any thoughts?We would use such a thing. Our databases use three partitions: log, data,
index. We currently create our databases like:CREATE DATABASE dbname OWNER owner TABLESPACE tsname;
We then specify another index tablespace on index creation (which really
isn't that difficult).Adding an INDEX_TABLESPACE option to CREATE DATABASE might be worthwhile if
what we have done is typical. Or if pg maintainers want to suggest this
usage as sensible.-K
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
"Jim C. Nasby" <jim@nasby.net> writes:
TODO?
%Add default_index_tablespace GUC and database parameter.
That was part of the original tablespace proposal and was rejected for
(what seemed at the time) good reasons. It'd be nice if this thread
betrayed any awareness whatsoever of the previous discussions ...
regards, tom lane
On Fri, Dec 02, 2005 at 06:06:25PM -0500, Tom Lane wrote:
"Jim C. Nasby" <jim@nasby.net> writes:
TODO?
%Add default_index_tablespace GUC and database parameter.That was part of the original tablespace proposal and was rejected for
(what seemed at the time) good reasons. It'd be nice if this thread
betrayed any awareness whatsoever of the previous discussions ...
Any idea on what to search for? 'default index tablespace' isn't turning
up anything that looks like that discussion...
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461