| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Final(?) proposal for wal_sync_method changes |
| Date: | 2010-12-10 02:47:46 |
| Message-ID: | 4D0194D2.3030102@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg,
> This is interesting, because test_fsync consistently reported a rate of
> about half this when using open_datasync instead of the equal
> performance I'm getting from the database. I'll see if I can reproduce
> that further, but it's no reason to be concerned about the change that's
> been made I think. Just more evidence that test_fsync has quirks left
> to be sorted out. But that's not backbranch material, it should be part
> of 9.1 only refactoring, already in progress via the patch Josh
> submitted. There's a bit of time left to get that done.
Did you rerun test_sync with O_DIRECT entabled, using my patch? The
figures you had from test_fsync earlier were without O_DIRECT.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2010-12-10 02:50:56 | Re: Final(?) proposal for wal_sync_method changes |
| Previous Message | Fujii Masao | 2010-12-10 02:46:50 | Re: Postgresql 9.1 pg_last_xact_replay_timestamp limitations |