From: | "Joshua J(dot) Kugler" <joshua(at)eeinternet(dot)com> |
---|---|
To: | "Fernando Hevia" <fhevia(at)ip-tel(dot)com(dot)ar> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Moving database cluster |
Date: | 2010-01-14 21:55:04 |
Message-ID: | 201001141255.04813.joshua@eeinternet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday 14 January 2010, Fernando Hevia elucidated thus:
> > The easiest way is to shut down Pg, move the 'main' directory
> > somewhere else, and then point a symlink to the new location.
>
> Thanks for your reply.
> I had considered this first but then I wasn't sure if there would be
> any performance penalty.
> The current main directory sits on a 'slow' RAID 1 volume while the
> new one will sit on a 'fast' 12 disk RAID 10 volume.
> I guess the symlink shouldn't be troublesome but I don't know if some
> PG process will continually be reading this link encumbering somehow
> the RAID 1 disks.
I'm not sure how Pg does it, but I remember reading several years ago
that MySQL would, upon startup, "resolve" the symlink, and use the real
path name for the rest of its execution. I would assume Pg does
something similar.
j
--
Joshua Kugler
Part-Time System Admin/Programmer
http://www.eeinternet.com
PGP Key: http://pgp.mit.edu/ ID 0x14EA086E
From | Date | Subject | |
---|---|---|---|
Next Message | Gauthier, Dave | 2010-01-14 22:12:16 | Avoid transaction abot if/when constraint violated |
Previous Message | Fernando Hevia | 2010-01-14 21:38:52 | Re: Moving database cluster |