Fwd: Bug#253295: postgresql: VACUUM FULL produce warnings

From: Martin Pitt <martin(at)piware(dot)de>
To: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Fwd: Bug#253295: postgresql: VACUUM FULL produce warnings
Date: 2004-06-23 08:29:55
Message-ID: 20040623082955.GB2995@donald.intranet.fbn-dd.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi PostgreSQL developers!

Recently we got the following bug report about VACUUM FULL. Can
anybody comment on this?

If you have questions concerning the submitter's configuration, can
you please ask him directly? (ed(at)divo(dot)ru)

Thanks in advance and have a nice day!

Martin

----- Forwarded message from Ed <ed(at)divo(dot)ru> -----

Subject: Bug#253295: postgresql: VACUUM FULL produce warnings
Reply-To: Ed <ed(at)divo(dot)ru>, 253295(at)bugs(dot)debian(dot)org
From: Ed <ed(at)divo(dot)ru>
To: Debian Bug Tracking System <submit(at)bugs(dot)debian(dot)org>
Date: Tue, 08 Jun 2004 17:19:13 +0400
X-Spam-Status: No, hits=0.0 required=4.0 tests=none autolearn=no version=2.61

Package: postgresql
Version: 7.4.2-3.backports.org.1
Severity: normal

i have small postgesql database with my own clients (C+libpq). database update are rare (several tens per day), transactions common (one or two every second)

if i run "VACUUM FULL" in psql i get several messages like this:

WARNING: index "pg_depend_depender_index" contains 3722 row versions, but table contains 3720 row versions

if i do REINDEX DATABASE before VACUUM i don't see any warnings.

it's normal behaviour? or i must look for problem source?

----- End forwarded message -----
----- Forwarded message from Oliver Elphick <olly(at)lfix(dot)co(dot)uk> -----

Subject: Bug#253295: postgresql: VACUUM FULL produce warnings
Reply-To: olly(at)lfix(dot)co(dot)uk, 253295(at)bugs(dot)debian(dot)org
From: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
To: Ed <ed(at)divo(dot)ru>, 253295(at)bugs(dot)debian(dot)org
Date: Tue, 08 Jun 2004 15:03:03 +0100
X-Spam-Status: No, hits=0.0 required=4.0 tests=none autolearn=no version=2.61

On Tue, 2004-06-08 at 14:19, Ed wrote:
> Package: postgresql
> Version: 7.4.2-3.backports.org.1
> Severity: normal
>
> i have small postgesql database with my own clients (C+libpq). database update are rare (several tens per day), transactions common (one or two every second)
>
>
> if i run "VACUUM FULL" in psql i get several messages like this:
>
> WARNING: index "pg_depend_depender_index" contains 3722 row versions, but table contains 3720 row versions
>
> if i do REINDEX DATABASE before VACUUM i don't see any warnings.
>
> it's normal behaviour? or i must look for problem source?

I wouldn't consider it normal. Reindexing will remove the problem, of
course. The question is how the problem arose in the first place (that
is, more row versions in the index than in the table itself).

Do all transactions terminate before you run VACUUM FULL?

Is it the case that this problem keeps recurring?

--
Oliver Elphick olly(at)lfix(dot)co(dot)uk
Isle of Wight http://www.lfix.co.uk/oliver
GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA
========================================
"Therefore being justified by faith, we have peace with
God through our Lord Jesus Christ." Romans 5:1

----- End forwarded message -----
----- Forwarded message from ed(at)divo(dot)ru -----

Subject: Bug#253295: Re[2]: Bug#253295: postgresql: VACUUM FULL produce
warnings
Reply-To: ed(at)divo(dot)ru, 253295(at)bugs(dot)debian(dot)org
From: ed(at)divo(dot)ru
Date: Wed, 9 Jun 2004 10:10:25 +0400
To: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
Cc: 253295(at)bugs(dot)debian(dot)org
X-Spam-Status: No, hits=0.2 required=4.0 tests=NO_REAL_NAME,
SUBJ_BRACKET_BALANCED,SUBJ_BRACKET_OFF,SUBJ_BRACKET_ON autolearn=no
version=2.61

OE> Do all transactions terminate before you run VACUUM FULL?

No. but i think it's not problem source:
- afaik VACUUM FULL must lock tables and can't start before
write-transactions done
- if i see this messages once - i get its every time VACUUM FULL
running, until i execute REINDEX DATABASE

OE> Is it the case that this problem keeps recurring?

i can't say when problem appear, but i see it every day on working
database.

what may be problem source? how can i find it?

- i found now AUTOVACUUM=yes in postmaster.conf, but
postgesql-contrib don't installed
- postgresql work over xfs filesystem on linux 2.6

----- End forwarded message -----

--
Martin Pitt Debian GNU/Linux Developer
martin(at)piware(dot)de mpitt(at)debian(dot)org
http://www.piware.de http://www.debian.org

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Martin Pitt 2004-06-23 08:34:22 Re: [Fwd: Bug#255208: postgresql - ignores SIGPIPE]
Previous Message Stephan Szabo 2004-06-23 04:21:16 Re: BUG #1180: incorrect date handling