From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | robert(at)interactive(dot)co(dot)uk, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Needs discussion of pg_xlog |
Date: | 2016-12-01 16:56:20 |
Message-ID: | 5414c450-db82-8169-d5cf-f33339d0944c@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 12/01/2016 07:00 AM, robert(at)interactive(dot)co(dot)uk wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.4/static/runtime-config-file-locations.html
> Description:
>
> In various places (e.g. stackoverflow), I've seen people suggest having
> pg_xlog ion a different disk (i.e. not in /var/lib/pgsql/9.X/data).
>
> The only mention of this that I've seen is in Section 29.5 (WAL Internals),
> and that just says "it is advantageous...", with no explanation.
>
> If this IS a good idea, then "Server Configuration / File Locations" is
> where it should be discussed: in particular, why is it a good idea, and how
> does it affect backups (and in particular base backups to a standby server).
The reason it can be advantageous is that pg_xlog has a different write
profile that $PGDATA. The WAL is written sequentially versus randomly.
JD
>
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
Unless otherwise stated, opinions are my own.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-12-01 18:50:13 | Re: Needs discussion of pg_xlog |
Previous Message | robert | 2016-12-01 15:00:06 | Needs discussion of pg_xlog |