| From: | "Mikel Lindsaar" <raasdnil(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Anyone successfully moved the pg_xlog to a separate drive on windows server? |
| Date: | 2008-04-11 07:52:48 |
| Message-ID: | 57a815bf0804110052s6e60ad56q1639f9f0451e21d6@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hello all,
I tried in vain last night to move the pg_xlog directory to another
drive to get some more speed out of our database.
To do this, I used linkd.exe from the Windows Server 2003 Resource
Kit. This tool creates a 'junction' (which is the Windows term for
symlink).
However, with the pg_xlog moved to the new drive, the junction created
and able to be navigated through on the command line and explorer,
when I start up Postgres it gives an error. I put all the details in a
bug report:
http://archives.postgresql.org/pgsql-bugs/2008-04/msg00084.php
But has anyone figured a work around on this?
I am still in negotiation with the powers that be to move over to a
BSD OS, but in the mean time I need to solve this somehow.
Any ideas?
Mikel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Baudrion Philippe | 2008-04-11 14:14:05 | Retore Postgres DB without dump |
| Previous Message | Jeff Frost | 2008-04-10 21:39:36 | updating table with foreign keys cause locking of referenced row/table? |