Re: Moving pg_xlog

From: Steven Winfield <Steven(dot)Winfield(at)cantabcapital(dot)com>
To: Lucas Possamai <drum(dot)lucas(at)gmail(dot)com>, 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 08:54:42
Message-ID: E9FA92C2921F31408041863B74EE4C20016B17D3D0@CCPMAILDAG03.cantab.local
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<mailto:michael(dot)paquier(at)gmail(dot)com>>:
On Fri, Dec 2, 2016 at 1:04 PM, Melvin Davidson <melvin6925(at)gmail(dot)com<mailto: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

It’s also worth mentioning that the xlog directory can be specified at cluster creation time using ‘initdb -X <directory>’, which (AFAICT) just creates the symlink for you.

Steve.

Dr. Steven Winfield
Scientist
D: +44 (0)1223 755 776

[Cantab email sig]

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alexander Farber 2016-12-02 09:52:03 Using UPDATE ... RETURNING in a custom SQL function, which RETURNS integer
Previous Message Job 2016-12-02 08:19:58 Postgresql 9.6 and Big Data