pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Return of the Solaris vacuum polling problem -- anyone remember this?
Date: Mon, 23 Aug 2010 12:47:28 -0400
Message-ID: <1282581999-sup-8560@alvh.no-ip.org> (raw)
In-Reply-To: <22915.1282581632@sss.pgh.pa.us>
References: <201008221651.o7MGplA28857@momjian.us>
	<1282579975-sup-2769@alvh.no-ip.org>
	<22915.1282581632@sss.pgh.pa.us>

Excerpts from Tom Lane's message of lun ago 23 12:40:32 -0400 2010:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > Excerpts from Bruce Momjian's message of dom ago 22 12:51:47 -0400 2010:
> >> Do you have a suggestion?  Reorder the items?
> 
> > I'd add another para before that one saying that this value "also"
> > affects pg_clog truncation.  I agree that putting pg_clog truncation as
> > the first item here is not an improvement.  For most people, having
> > those pg_clog files there or not is going to be a wash, compared to data
> > size.
> 
> I was going to suggest that the point about pg_clog should be in a
> separate paragraph *after* this one, since it seems like a secondary
> issue.  But anyway, I agree with putting this para back as it was and
> talking about clog in a separate para.

Sorry, yes, I was also thinking "after".  I don't know what made me
write "before" but it wasn't clarity of thought.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



view thread (31+ messages)  latest in thread

Message-ID: <1282581999-sup-8560@alvh.no-ip.org>
Permalink:  ../1282581999-sup-8560@alvh.no-ip.org/
Also on:    postgresql.org/message-id/1282581999-sup-8560@alvh.no-ip.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: alvherre@commandprompt.com, tgl@sss.pgh.pa.us, bruce@momjian.us, josh@agliodbs.com
  Subject: Re: Return of the Solaris vacuum polling problem -- anyone remember this?
  In-Reply-To: <1282581999-sup-8560@alvh.no-ip.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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