Zdenek Kotala wrote:
> But how it was mentioned in this thread maybe
> somethink like this "CREATE TABLESPACE name LOCATION '/my/location'
> SEGMENTS 10GB" should good solution. If segments is not mentioned then
> default value is used.
I think you would need a tool to resegmentize a table or tablespace offline,
usable for example when recovering a backup.
Also, tablespace configuration information is of course also stored in a
table. pg_tablespace probably won't become large, but it would probably
still need to be special-cased, along with other system catalogs perhaps.
An then, how to coordindate offline resegmenting and online tablespace
operations in a crash-safe way?
Another factor I just thought of is that tar, commonly used as part of a
backup procedure, can on some systems only handle files up to 8 GB in size.
There are supposed to be newer formats that can avoid that restriction, but
it's not clear how widely available these are and what the incantation is to
get at them. Of course we don't use tar directly, but if we ever make large
segments the default, we ought to provide some clear advice for the user on
how to make their backups.
In response to
pgsql-hackers by date
|Next:||From: Richard Huxton||Date: 2008-03-19 08:56:54|
|Subject: Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence
for encoding "UTF8": 0xc3|
|Previous:||From: Zdeněk Kotala||Date: 2008-03-19 08:33:57|
|Subject: Re: regress test problems|
pgsql-patches by date
|Next:||From: Martijn van Oosterhout||Date: 2008-03-19 09:51:12|
|Subject: Re: [PATCHES] Fix for large file support (nonsegment mode support)|
|Previous:||From: KaiGai Kohei||Date: 2008-03-19 05:55:58|
|Subject: Re: [PATCHES] [0/4] Proposal of SE-PostgreSQL patches|