pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Steve Crawford <scrawford@pinpointresearch.com>
Cc: Peter Kovacs <maxottovonstirlitz@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Do we need vacuuming when tables are regularly dropped?
Date: Mon, 29 Sep 2008 18:45:53 -0400
Message-ID: <25195.1222728353@sss.pgh.pa.us> (raw)
In-Reply-To: <dcc563d10809291026h6d01e20cv1afcffd8aec332c5@mail.gmail.com>
References: <b6e8f2e80809290237p7685dbcfm9d5c886ba225b956@mail.gmail.com>
	<9815.1222690583@sss.pgh.pa.us>
	<b6e8f2e80809290533g2a7e09b1i110bb085ad75092e@mail.gmail.com>
	<48E10C95.2050207@pinpointresearch.com>
	<dcc563d10809291026h6d01e20cv1afcffd8aec332c5@mail.gmail.com>

"Scott Marlowe" <scott.marlowe@gmail.com> writes:
> Also, there was a time when you couldn't do vacuum full on system
> tables do to locking issues, and had to take the db down to single
> user mode to do so.

There was a short period when *concurrent* vacuum fulls on just the
wrong combinations of system catalogs could deadlock (because they both
needed to look up stuff in the other one).  AFAIK we fixed that.  It's
never been the case that it didn't work at all.

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <25195.1222728353@sss.pgh.pa.us>
Permalink:  ../25195.1222728353@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/25195.1222728353@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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, scott.marlowe@gmail.com, scrawford@pinpointresearch.com, maxottovonstirlitz@gmail.com
  Subject: Re: Do we need vacuuming when tables are regularly dropped?
  In-Reply-To: <25195.1222728353@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