Re: pgsql: Improve wording.

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-committers(at)alvh(dot)no-ip(dot)org
Subject: Re: pgsql: Improve wording.
Date: 2007-12-18 12:32:51
Message-ID: 20071218123251.GD5319@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Martijn van Oosterhout wrote:
> On Mon, Dec 17, 2007 at 01:48:31PM +0000, Alvaro Herrera wrote:
> > Log Message:
> > -----------
> > Improve wording.

> I'd suggest removing everything between the parentheses, or perhaps
> something like: By tracking allocated memory rather than used memory
> it removes the possibilty of failing in a page fault. This option also
> require you allocate enoghh swap to cover all possible eventualities,
> though in production it will not be used.

I agree that the parenthised phrase should be removed.

http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/runtime.sgml?r1=1.387&r2=1.391

I think your proposed wording is removed enough from what the
complainant was saying that it is not worth to stick it in. The point
here is, to what extent do we want to spoon-feed careless sysadmins?

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-12-18 15:07:37 Re: pgsql: Improve wording.
Previous Message Martijn van Oosterhout 2007-12-18 11:30:08 Re: pgsql: Improve wording.

Browse pgsql-hackers by date

  From Date Subject
Next Message peter.trautmeier 2007-12-18 13:48:23 Re: ecxt_scantuple has wrong TupleDesc
Previous Message Martijn van Oosterhout 2007-12-18 11:30:08 Re: pgsql: Improve wording.