| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Streaming replication on win32, still broken |
| Date: | 2010-02-19 10:54:50 |
| Message-ID: | 4B7E6DFA.9090200@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
>> quicker.
>
> 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?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-02-19 11:52:54 | Re: testing cvs HEAD - HS/SR - PANIC: cannot make new WAL entries during recovery |
| Previous Message | Simon Riggs | 2010-02-19 10:51:14 | Re: Re: [COMMITTERS] pgsql: Introduce WAL records to log reuse of btree pages, allowing |