pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: James Farrugia <james.farrugia@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Orphan TOAST object
Date: Mon, 12 May 2008 10:08:55 -0400
Message-ID: <18954.1210601335@sss.pgh.pa.us> (raw)
In-Reply-To: <8d01be800805120025u3a49fa39rc7033a2480b4982f@mail.gmail.com>
References: <8d01be800805110946r792efacdp3dbe02829b6da7a9@mail.gmail.com>
	<20553.1210525788@sss.pgh.pa.us>
	<8d01be800805111017w6910acdapaf66f0b56908d36e@mail.gmail.com>
	<20763.1210526763@sss.pgh.pa.us>
	<8d01be800805120025u3a49fa39rc7033a2480b4982f@mail.gmail.com>

"James Farrugia" <james.farrugia@gmail.com> writes:
> One last thing...can we run into data-loss problems with successfully
> vacuumed tables even if there is one unvacuumed database object; what would
> have happened if I ignored to vacuum that rogue pg_toast (which was the only
> unvacuumed object within the entire database)?

The database would have shut down when you got to the
2-billion-transactions mark.  So you'd have had to solve the problem
sooner or later anyway.

			regards, tom lane

view thread (8+ messages)  latest in thread

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

copy link · copy postgr.es

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, james.farrugia@gmail.com
  Subject: Re: Orphan TOAST object
  In-Reply-To: <18954.1210601335@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