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

help / color / mirror / Atom feed

From: Simon Riggs <simon@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: John Lister <john.lister-ps@kickstone.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Database corruption help
Date: Sun, 15 Feb 2009 10:18:10 +0000
Message-ID: <1234693090.4500.1142.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <3161.1234541940@sss.pgh.pa.us>
References: <507152DDF8AB4DF093BD01A8BEC7C659@squarepi.com>
	<17205.1234200693@sss.pgh.pa.us>
	<AB15E89CD7FB4EBD9D76CC5F8D8B3D4E@squarepi.com>
	<4990840C.4090900@kickstone.com>
	<20151.1234208044@sss.pgh.pa.us>
	<49908D72.7040904@kickstone.com>
	<25753.1234224090@sss.pgh.pa.us>
	<4991338B.704@kickstone.com>
	<4994906B.6090408@kickstone.com>
	<17204.1234474784@sss.pgh.pa.us>
	<4994987F.1030204@kickstone.com>
	<17764.1234476783@sss.pgh.pa.us>
	<4994A45B.4030707@kickstone.com>
	<49952D33.3000707@kickstone.com>
	<3161.1234541940@sss.pgh.pa.us>


On Fri, 2009-02-13 at 11:19 -0500, Tom Lane wrote:

> Aside from the "how did this happen" puzzle, the real point of any
> investigation of course ought to be whether we can make heap_page_prune
> more robust.  At the very least it's undesirable to be leaving the page
> in a state where VACUUM FULL will decide it can't shrink.

I think it would be useful to have a function that can scan a table to
see if this issue exists. ISTM if it has happened once it can have
happened many times. It would be useful to have some more trouble
reports so we can assess the size and scope of this problem.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support

view thread (19+ messages)  latest in thread

Message-ID: <1234693090.4500.1142.camel@ebony.2ndQuadrant>
Permalink:  ../1234693090.4500.1142.camel@ebony.2ndQuadrant/
Also on:    postgresql.org/message-id/1234693090.4500.1142.camel@ebony.2ndQuadrant

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: simon@2ndQuadrant.com, tgl@sss.pgh.pa.us, john.lister-ps@kickstone.com, pgsql-hackers@postgresql.org
  Subject: Re: Database corruption help
  In-Reply-To: <1234693090.4500.1142.camel@ebony.2ndQuadrant>

* 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