pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Palle Girgensohn <girgen@partitur.se>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: pg_attribute_relid_attnam_index problem after log disk filled up
Date: Tue, 29 Aug 2000 05:33:08 +0200
Message-ID: <39AB2EF4.B30F2466@partitur.se> (raw)
References: <39AA8BC3.3047D8CF@partitur.se>
	<19689.967510098@sss.pgh.pa.us>

Tom Lane wrote:
> 
> Palle Girgensohn <girgen@partitur.se> writes:
> > What's this? What to do? Shall I bother?
> 
> > pp=> vacuum;
> > NOTICE:  Index pg_attribute_relid_attnam_index: NUMBER OF
> > INDEX' TUPLES (3094) IS NOT THE SAME AS HEAP' (3093)
> 
> Under 6.5, if vacuum doesn't get rid of the message then I think the
> only way to do so is to dump and reload the database.  (I'd strongly
> recommend updating to 7.0.2 while you do that.)
> 
> The message in itself is not catastrophic, but it does raise the
> question of what other damage there might be.  Updating would be
> a good idea anyway, considering all the bugs that got fixed between
> 6.5 and 7.0.

I continued this discussion, in more depth, on the pgsql-admin
list. I finally "gave up" and dumped|restored, updating not
7.0.2, but 6.5.3, since we are not just ready testing our
application with pg7 yet. soon. There are som futile, but
still, SQL differences.

> > The problem started when the log partition (where
> > postmaster logging output is written) was full, and some
> > backends crashed.
> 
> Did they actually crash, or just hang up waiting for space to become
> available for the log file?  That really shouldn't have been much of
> a problem, AFAICS.

Crashed when I killed them, if memory serves me (maybe the sig
6 ones, but I can't verify 100%).

$ dmesg
.....
pid 52915 (postgres), uid 70 on /usr/local: file system full
[logging was to /usr/local  *blush* :-/ ]
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 52915 (postgres), uid 70 on /usr/local: file system full
pid 53230 (postgres), uid 70: exited on signal 6 (core dumped)
pid 53357 (postgres), uid 70: exited on signal 6 (core dumped)
pid 53479 (postgres), uid 70: exited on signal 11 (core dumped)
pid 53481 (postgres), uid 70: exited on signal 11 (core dumped)
pid 53505 (postgres), uid 70: exited on signal 11 (core dumped)
pid 53510 (postgres), uid 70: exited on signal 11 (core dumped)


Cheers,
Palle



view thread (3+ messages)

Message-ID: <39AB2EF4.B30F2466@partitur.se>
Permalink:  ../39AB2EF4.B30F2466@partitur.se/
Also on:    postgresql.org/message-id/39AB2EF4.B30F2466@partitur.se

 · 

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-sql@postgresql.org
  Cc: girgen@partitur.se, tgl@sss.pgh.pa.us
  Subject: Re: pg_attribute_relid_attnam_index problem after log disk filled up
  In-Reply-To: <39AB2EF4.B30F2466@partitur.se>
  References: <39AA8BC3.3047D8CF@partitur.se> <19689.967510098@sss.pgh.pa.us> <39AB2EF4.B30F2466@partitur.se>

* 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