Hi,
On some corner cases our database servers starts to use from swap space
and that totally makes PostgreSQL (or any other I/O bound application)
to fall upon its knees. In our current structure, responsiveness has the
highest priority and thus it is ok for us to cancel queries at that
instant and re-initiate connections. To achieve this effect, I started
to turn swap space off on some of the servers and turned
vm.oom_kill_allocating_task kernel parameter on. (Periodical postgres
process availability checks decides whether there is a need to fire up a
fresh postgres instance.) So far, this method worked pretty well but I'm
suspicious about data corruptions. (Disks configurations are set to RAID
10.) What are the downsides of such a design scheme?
Regards.
--
Sent via pgsql-general mailing list (pgsql-general@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
