Re: Moving pg_xlog

Поиск
Список
Период
Сортировка
От Lucas Possamai
Тема Re: Moving pg_xlog
Дата
Msg-id CAE_gQfVhgwXm8YsDFUPvtU5+yqmq_vJQ4p=Px22O_vnxVWk-Jw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Moving pg_xlog  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: Moving pg_xlog
Список pgsql-general
2016-12-02 17:10 GMT+13:00 Michael Paquier <michael.paquier@gmail.com>:
On Fri, Dec 2, 2016 at 1:04 PM, Melvin Davidson <melvin6925@gmail.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

В списке pgsql-general по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Moving pg_xlog
Следующее
От: Job
Дата:
Сообщение: R: CachedPlan logs until full disk