pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedDirect I/O versus OS-Caching
2+ messages / 2 participants
[nested] [flat]
* Direct I/O versus OS-Caching
@ 2005-06-28 11:55 KÖPFERL Robert <robert.koepferl@sonorys.at>
0 siblings, 1 reply; 2+ messages in thread
From: KÖPFERL Robert @ 2005-06-28 11:55 UTC (permalink / raw)
To: ; +Cc: pgsql-admin
Yeah, as the subject quetiones.
What's the better/faster alternative?
Enabling OS-file system caching or disabling it and forcing direct I/O?
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Direct I/O versus OS-Caching
@ 2005-06-28 13:10 Peter Eisentraut <peter_e@gmx.net>
parent: KÖPFERL Robert <robert.koepferl@sonorys.at>
0 siblings, 0 replies; 2+ messages in thread
From: Peter Eisentraut @ 2005-06-28 13:10 UTC (permalink / raw)
To: KÖPFERL Robert <robert.koepferl@sonorys.at>; +Cc: pgsql-admin
KÖPFERL Robert wrote:
> What's the better/faster alternative?
> Enabling OS-file system caching or disabling it and forcing direct
> I/O?
PostgreSQL is designed to rely on OS file-system caching, so you better
not turn that off.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2005-06-28 13:10 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-06-28 11:55 Direct I/O versus OS-Caching KÖPFERL Robert <robert.koepferl@sonorys.at>
2005-06-28 13:10 ` Peter Eisentraut <peter_e@gmx.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox