Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] bgwriter_lru_multiplier blurbs inconsistent

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Smith <gsmith(at)gregsmith(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-docs(at)postgresql(dot)org, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] bgwriter_lru_multiplier blurbs inconsistent
Date: 2008-03-06 16:32:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docspgsql-hackers
Tom Lane wrote:
> Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> > On Sun, 20 Jan 2008, Tom Lane wrote:
> >> I think the main problem is the qualifying clause up front in a place
> >> of prominence.  Here's a V3 try
> > That one looks good to me.  These are small details but better to get it 
> > right now.
> OK, committed.  Back to Alvaro's original concern: is the short
> description in guc.c all right, or can we improve that?

I have tried to improve the GUC description for
"bgwriter_lru_multiplier";  applied to CVS HEAD.

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + If your life is a hard drive, Christ can be your backup. +

Attachment: /rtmp/diff
Description: text/x-diff (777 bytes)

In response to

pgsql-docs by date

Next:From: Bruce MomjianDate: 2008-03-06 18:50:36
Subject: Re: [GENERAL] advisory locks: documentation hint and feature request
Previous:From: Bruce MomjianDate: 2008-03-06 15:39:05
Subject: Re: Lack of docs for libpq C Library

pgsql-hackers by date

Next:From: Richard HuxtonDate: 2008-03-06 17:17:28
Subject: Intended behaviour of SET search_path with SQL functions?
Previous:From: Magnus HaganderDate: 2008-03-06 16:21:10
Subject: Re: BUG #3909: src\tools\msvc\clean.bat clears parse.h file

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group