Re: Change Hard Disc Drive

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Yan Cheng Cheok <yccheok(at)yahoo(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Change Hard Disc Drive
Date: 2010-01-13 05:43:25
Message-ID: 4B4D5D7D.4000103@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 13/01/2010 1:31 PM, Dave Page wrote:
> On Wed, Jan 13, 2010 at 10:57 AM, Craig Ringer
> <craig(at)postnewspapers(dot)com(dot)au> wrote:
>> Unfortunately, it doesn't. This means you need to alter the Windows service
>> directly. What you need to do is stop the PostgreSQL service, then move your
>> data directory (by default in C:\Program Files\PostgreSQL\version\data where
>> "version" is 8.4, 8.3, etc) to the new location, and finally modify the
>> command line used by the service so Pg knows where to find its data
>> directory.
>
> Or... create a new tablespace on the larger drive using pgAdmin, and
> then move large tables/indexes across by right-clicking them and
> selecting Properties, and then choosing the new tablespace.

Good point. The OP said "all databases" but that may actually not be
what they need.

In fact, having tablespaces spread across both drives should give them
some performance benefits (xlog on original drive, big tables on other
drive) ... though it *does* expose them to losing the entire cluster if
EITHER drive fails. Good backups become even more essential.

--
Craig Ringer

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2010-01-13 06:18:25 Re: crosstab function - pivot - use column value as column description
Previous Message Vincenzo Romano 2010-01-13 05:38:06 R: Re: Weird EXECUTE ... USING behaviour