Heikki Linnakangas wrote:
> Magnus Hagander wrote:
>> Well, it's going to make the process that reads the WAL cause actual
>> physical I/O... That'll take a chunk out of your total available I/O,
>> which is likely to push you to the limit of your I/O capacity much
> Right, doesn't seem sensible, though it would be nice to see a benchmark
> on that.
> Here's a patch to disable O_DIRECT when archiving or streaming is
> enabled. This is pretty hard to test, so any extra eyeballs would be nice..
Committed. Can you check that this fixed the PANIC you saw?
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2010-02-19 11:52:54|
|Subject: Re: testing cvs HEAD - HS/SR - PANIC: cannot make new
WAL entries during recovery|
|Previous:||From: Simon Riggs||Date: 2010-02-19 10:51:14|
|Subject: Re: Re: [COMMITTERS] pgsql: Introduce WAL records to log
reuse of btree pages, allowing|