Thanks, everyone, for your comments.
I think I've got a clearer idea of what's going on now...
Robert.
On 1 December 2016 at 13:55, Robert Inder wrote:
> I'm running Postgres9.4 in master/hot-standby mode on a few pairs of servers.
>
> While recovering from A Bit Of Bother last week, I came a
On Thu, Dec 1, 2016 at 6:17 PM, Michael Paquier
wrote:
> On Thu, Dec 01, 2016 at 05:48:51PM +0200, Achilleas Mantzios wrote:
> >
> > Performance is the reason. You would benefit from moving pg_xlog to a
> > different controller with its own write cache or to a different SSD with
> a
> > write cac
2016-12-02 17:10 GMT+13:00 Michael Paquier
mailto:michael.paqu...@gmail.com>>:
On Fri, Dec 2, 2016 at 1:04 PM, Melvin Davidson
mailto:melvin6...@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 PostgreS
2016-12-02 17:10 GMT+13:00 Michael Paquier :
> On Fri, Dec 2, 2016 at 1:04 PM, Melvin Davidson
> 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 parti
On Fri, Dec 2, 2016 at 1:04 PM, Melvin Davidson 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 p
On Thu, Dec 1, 2016 at 10:17 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Thu, Dec 1, 2016 at 7:59 PM, Jeff Janes wrote:
>
>> On Thu, Dec 1, 2016 at 5:55 AM, Robert Inder
>> wrote:
>>
>>>
>>> I'd really like to read an explicit discussion of this in the official
>>> documentat
On Thu, Dec 1, 2016 at 7:59 PM, Jeff Janes wrote:
> On Thu, Dec 1, 2016 at 5:55 AM, Robert Inder
> wrote:
>
>>
>> I'd really like to read an explicit discussion of this in the official
>> documentation, rather than just glean what I can from answers to
>> questions.
>>
>
> The official documenta
On Thu, Dec 1, 2016 at 5:55 AM, Robert Inder
wrote:
> I'm running Postgres9.4 in master/hot-standby mode on a few pairs of
> servers.
>
> While recovering from A Bit Of Bother last week, I came across a
> posting saying that pg_xlog should be on a separate partition.
>
> I tried to find out more
On Thu, Dec 01, 2016 at 05:48:51PM +0200, Achilleas Mantzios wrote:
> On 01/12/2016 15:55, Robert Inder wrote:
> > I'm running Postgres9.4 in master/hot-standby mode on a few pairs of
> > servers.
> >
> > While recovering from A Bit Of Bother last week, I came across a
> > posting saying that pg
On 01/12/2016 15:55, Robert Inder wrote:
I'm running Postgres9.4 in master/hot-standby mode on a few pairs of servers.
While recovering from A Bit Of Bother last week, I came across a
posting saying that pg_xlog should be on a separate partition.
I tried to find out more about this, by consult
I'm running Postgres9.4 in master/hot-standby mode on a few pairs of servers.
While recovering from A Bit Of Bother last week, I came across a
posting saying that pg_xlog should be on a separate partition.
I tried to find out more about this, by consulting the PostgresQL
documentation (i.e.
http
On Mon, 4 Jun 2007, Steve Atkins wrote:
Are you running SELinux? It's main goal in life is to break disk access by
denying permission to files anywhere other than where it thinks an
application should be allowed to access.
Bleh. I am, but I *thought* it was not enforcing. Seems I was wrong.
On Jun 4, 2007, at 11:15 AM, Ben wrote:
On Mon, 4 Jun 2007, Joshua D. Drake wrote:
Ben wrote:
I'm trying to move my WAL to another drive, but am having
difficulties with this seemingly simple process. Every time I
start up with pg_xlog symlinked to my other drive, I get this:
FATAL: coul
On Mon, 4 Jun 2007, Joshua D. Drake wrote:
Ben wrote:
I'm trying to move my WAL to another drive, but am having difficulties with
this seemingly simple process. Every time I start up with pg_xlog symlinked
to my other drive, I get this:
FATAL: could not open file "pg_xlog/0001.history":
Ben wrote:
> I'm trying to move my WAL to another drive, but am having difficulties
> with this seemingly simple process. Every time I start up with pg_xlog
> symlinked to my other drive, I get this:
>
> FATAL: could not open file "pg_xlog/0001.history": Permission denied
>
> If I move pg_
Ben wrote:
I'm trying to move my WAL to another drive, but am having difficulties
with this seemingly simple process. Every time I start up with pg_xlog
symlinked to my other drive, I get this:
FATAL: could not open file "pg_xlog/0001.history": Permission denied
If I move pg_xlog back in
I'm trying to move my WAL to another drive, but am having difficulties
with this seemingly simple process. Every time I start up with pg_xlog
symlinked to my other drive, I get this:
FATAL: could not open file "pg_xlog/0001.history": Permission denied
If I move pg_xlog back into its norma
17 matches
Mail list logo
