| From: | Lucas Possamai <drum(dot)lucas(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Melvin Davidson <melvin6925(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Robert Inder <robert(at)interactive(dot)co(dot)uk>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Moving pg_xlog |
| Date: | 2016-12-02 06:51:08 |
| Message-ID: | CAE_gQfVhgwXm8YsDFUPvtU5+yqmq_vJQ4p=Px22O_vnxVWk-Jw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2016-12-02 17:10 GMT+13:00 Michael Paquier <michael(dot)paquier(at)gmail(dot)com>:
> On Fri, Dec 2, 2016 at 1:04 PM, Melvin Davidson <melvin6925(at)gmail(dot)com>
> wrote:
> > Well, while the location of pg_xlog is not currently configurable, on
> Linux system the way to do it is to:
> > 1. stop PostgreSQL
> > 2. move the pg_xlog directory to a separate partition
> > 3. create a symbolic link to point to the new partition
> > 4. restart PostgreSQL
>
> Similar flow on Windows, just use a junction point for the link.
> --
> Michael
>
I've done this on my Postgres 9.2 DB server running CentOS 6.7...
And it's pretty much what the guys told you already:
> 1. stop PostgreSQL
> 2. move the pg_xlog directory to a separate partition
> 3. create a symbolic link to point to the new partition
> 4. restart PostgreSQL
In my case, it significantly improved I/O performance.
Lucas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Job | 2016-12-02 07:27:29 | R: CachedPlan logs until full disk |
| Previous Message | Michael Paquier | 2016-12-02 04:10:03 | Re: Moving pg_xlog |