pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matthew T. O'Connor <matthew@zeut.net>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Jeff Boes <jboes@nexcerpt.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: pg_autovacuum crashes when query fails for temp tables
Date: Wed, 21 Apr 2004 00:38:52 -0400
Message-ID: <26127.1082522332@sss.pgh.pa.us> (raw)
In-Reply-To: <4085EE81.9080309@zeut.net>
References: <200404201525.i3KFPp809934@candle.pha.pa.us>
	<4085D554.9010802@familyhealth.com.au>
	<4085EE81.9080309@zeut.net>

"Matthew T. O'Connor" <matthew@zeut.net> writes:
> System Tables:  pg_autovacuum treats non-shared system tables just like 
> any other table.  It monitors the activity and vacuums when it deems it 
> appropriate.  As for shared system tables: In user databases they are 
> only analyzed by pg_autovacuum, while connected to template1, 
> pg_autovacuum will treat the shared tables as normal tables and vacuum 
> when appropriate.

As long as you hit template1 reasonably often, this will work.  But I'm
a bit concerned about the possibility that some maverick will decide he
doesn't need template1.  (It's at least theoretically possible to run
without it.)

Plan B would be to ignore the sharedness issue and vacuum/analyze shared
catalogs the same as anything else.  While this would certainly result
in more vacuums than really necessary, these tables are probably small
enough that it'd hardly matter ...

Comments?

			regards, tom lane



view thread (16+ messages)  latest in thread

Message-ID: <26127.1082522332@sss.pgh.pa.us>
Permalink:  ../26127.1082522332@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/26127.1082522332@sss.pgh.pa.us

 · 

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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, matthew@zeut.net, chriskl@familyhealth.com.au, pgman@candle.pha.pa.us, jboes@nexcerpt.com, pgsql-hackers@postgresql.org
  Subject: Re: pg_autovacuum crashes when query fails for temp tables
  In-Reply-To: <26127.1082522332@sss.pgh.pa.us>
  References: <200404201525.i3KFPp809934@candle.pha.pa.us> <4085D554.9010802@familyhealth.com.au> <4085EE81.9080309@zeut.net> <26127.1082522332@sss.pgh.pa.us>

* 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