pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-hackers@postgresql.org
Subject: Re: pg_autovacuum crashes when query fails for temp
Date: Tue, 20 Apr 2004 22:24:21 -0400
Message-ID: <m33c6y6pbe.fsf@wolfe.cbbrowne.com> (raw)
References: <200404201525.i3KFPp809934@candle.pha.pa.us>
	<40855DF0.3010300@idigx.com>
	<37398.192.154.91.225.1082485149.squirrel@192.154.91.225>

matthew@zeut.net ("Matthew T. O'Connor") wrote:
>> Bruce Momjian wrote:
>> Should pg_autovacuum be vacuuming temporary tables?
>
> This is a good question, and I would like some opinions from some other
> people more informed than I.
>
>> Secondly, why would
>> a temporary table for another session be visible to pg_autovacuum?  I
>> know these may sound like stupid questions, but I'm a little shocked
>> that it found a temp table.  Did someone make a permanent table, delete
>> it, and pg_autovacuum found it in between those operations?
>
> I will look into this when I have time, it certainly would be possible
> that pg_autovacuum could be tripped up by a sequence of events like you
> describe above.  The more general problem is that it shouldn't crash even
> if it's vacuuming tables it shouldn't.

Well, there's an entry in pg_class even for temporary tables; that
means that even though a separate session has no ability to vacuum the
table, there is still a way to get at its name.

I would think that temp tables are TERRIBLE candidates for
auto-vacuuming; they are likely to be created via INSERT or SELECT
INTO, and if there is a need to analyze such a table, it is likely
needful to do so under strict application control.
-- 
let name="cbbrowne" and tld="acm.org" in String.concat "@" [name;tld];;
http://www3.sympatico.ca/cbbrowne/advocacy.html
Rules of  the Evil Overlord #196.  "I will hire an  expert marksman to
stand by the entrance to my  fortress. His job will be to shoot anyone
who rides up to challenge me."  <http://www.eviloverlord.com/;



view thread (16+ messages)  latest in thread

Message-ID: <m33c6y6pbe.fsf@wolfe.cbbrowne.com>
Permalink:  ../m33c6y6pbe.fsf@wolfe.cbbrowne.com/
Also on:    postgresql.org/message-id/m33c6y6pbe.fsf@wolfe.cbbrowne.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-admin@postgresql.org
  Cc: cbbrowne@acm.org, pgsql-hackers@postgresql.org
  Subject: Re: pg_autovacuum crashes when query fails for temp
  In-Reply-To: <m33c6y6pbe.fsf@wolfe.cbbrowne.com>
  References: <200404201525.i3KFPp809934@candle.pha.pa.us> <40855DF0.3010300@idigx.com> <37398.192.154.91.225.1082485149.squirrel@192.154.91.225> <m33c6y6pbe.fsf@wolfe.cbbrowne.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