pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steven Flatt <steven.flatt@gmail.com>
To: Jim Nasby <decibel@decibel.org>
Cc: Bill Moran <wmoran@collaborativefusion.com>
Cc: Francisco Reyes <lists@stringsutils.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Database-wide VACUUM ANALYZE
Date: Tue, 26 Jun 2007 13:25:44 -0400
Message-ID: <357fa7590706261025l5b9cf016p7c61505643aabb9c@mail.gmail.com> (raw)
In-Reply-To: <FFD6DF28-B30D-47D0-BFB5-6485B32BF8AC@decibel.org>
References: <357fa7590706211009w2ef6071fn83c5759db6be1e80@mail.gmail.com>
	<cone.1182452313.269532.11564.5001@35st.simplicato.com>
	<357fa7590706211236y2856ed96q5394b9302b9a528f@mail.gmail.com>
	<20070621160732.58497e2b.wmoran@collaborativefusion.com>
	<357fa7590706211337i55e9b20nea5a1bd4c5e41268@mail.gmail.com>
	<FFD6DF28-B30D-47D0-BFB5-6485B32BF8AC@decibel.org>

On 6/25/07, Jim Nasby <decibel@decibel.org> wrote:
>
> If you set that to 2B, that means you're 2^31-"2 billion"-1000000
> transactions away from a shutdown when autovac finally gets around to
> trying to run a wraparound vacuum on a table. If you have any number
> of large tables, that could be a big problem, as autovac could get
> tied up on a large table for a long enough period that the table
> needing to be frozen doesn't get frozen in time.
>
> I suspect 1B is a much better setting. I probably wouldn't go past 1.5B.

view thread (11+ messages)  latest in thread

Message-ID: <357fa7590706261025l5b9cf016p7c61505643aabb9c@mail.gmail.com>
Permalink:  ../357fa7590706261025l5b9cf016p7c61505643aabb9c@mail.gmail.com/
Also on:    postgresql.org/message-id/357fa7590706261025l5b9cf016p7c61505643aabb9c@mail.gmail.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: steven.flatt@gmail.com, decibel@decibel.org, wmoran@collaborativefusion.com, lists@stringsutils.com
  Subject: Re: Database-wide VACUUM ANALYZE
  In-Reply-To: <357fa7590706261025l5b9cf016p7c61505643aabb9c@mail.gmail.com>
  References: <357fa7590706211009w2ef6071fn83c5759db6be1e80@mail.gmail.com> <cone.1182452313.269532.11564.5001@35st.simplicato.com> <357fa7590706211236y2856ed96q5394b9302b9a528f@mail.gmail.com> <20070621160732.58497e2b.wmoran@collaborativefusion.com> <357fa7590706211337i55e9b20nea5a1bd4c5e41268@mail.gmail.com> <FFD6DF28-B30D-47D0-BFB5-6485B32BF8AC@decibel.org> <357fa7590706261025l5b9cf016p7c61505643aabb9c@mail.gmail.com>

* 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