Re: gcc: why optimize for size flag is not the default

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: gcc: why optimize for size flag is not the default
Date: 2009-03-11 20:09:06
Message-ID: 20090311200905.GI4009@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

A.M. wrote:

> That said, if postgresql is paging out, the DBA probably has postgresql
> or the server misconfigured.

Keep in mind that "paging in" in this context also means moving stuff
from plain RAM into cache.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-03-11 20:38:50 Broken stuff in new dtrace probes
Previous Message A.M. 2009-03-11 19:31:33 Re: gcc: why optimize for size flag is not the default