Received: from bastuba.partitur.se ([212.209.169.194]) by hub.org (8.10.1/8.10.1) with ESMTP id e7T3XAC19692 for ; Mon, 28 Aug 2000 23:33:10 -0400 (EDT) Received: from stordatan.palle.se (c193.150.250.87.cm-upc.chello.se [193.150.250.87]) by bastuba.partitur.se (8.9.3/8.9.3) with ESMTP id FAA73612; Tue, 29 Aug 2000 05:33:08 +0200 (CEST) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.palle.se (8.9.3/8.9.3) with ESMTP id FAA14250; Tue, 29 Aug 2000 05:33:08 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <39AB2EF4.B30F2466@partitur.se> Date: Tue, 29 Aug 2000 05:33:08 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: Tom Lane CC: pgsql-sql@postgresql.org Subject: Re: pg_attribute_relid_attnam_index problem after log disk filled up References: <39AA8BC3.3047D8CF@partitur.se> <19689.967510098@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200008/316 Tom Lane wrote: > > Palle Girgensohn 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