From: | Jason Buberel <jason(at)altosresearch(dot)com> |
---|---|
To: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Cc: | "Tom Sparks (Applied Operations)" <tsparks(at)appliedops(dot)net> |
Subject: | Time to move table to new tablespace |
Date: | 2012-01-07 14:52:13 |
Message-ID: | CAAPEApExVTTUKQcN262FNtWXLOQzKuyY4gtpgo_NLkLtHaUSug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm considering the migration of an existing large (2.3TB) table to a new
tablespace. The table size, according to the '\dt+' command:
public | city_summary | table | altosresearch | 2345 GB |
Are there any considerations - besides the usual disk and network IO
constraints - that I need to take into account when estimating the amount
of time that would be required for the following commands to complete?
psql> create tablespace 'newstorage' location '/some/new/path';
psql> alter table city_summary set tablespace = 'newstorage';
Any other recommendations are welcome, such as "You are an idiot for not
using partitioning in the first place" :)
--
Jason L. Buberel
CTO, Altos Research
http://www.altosresearch.com/
650.603.0907
From | Date | Subject | |
---|---|---|---|
Next Message | Phoenix Kiula | 2012-01-07 15:40:57 | Re: URGENT: temporary table not recognized? |
Previous Message | Dmitriy Igrishin | 2012-01-07 10:05:24 | Re: How to code lo_creat & lo_write & lo_read in non-blocking mode |