Re: pg_group_name_index corrupt?

The Hermit Hacker <scrappy@hub.org> writes:
> Hadn't thought of that ... but ... and you aren't going to like this
> ... if I delete/vacuum/insert/vacuum ... INDEX TUPLES increases by 1, HEAP
> increases by one ... I'm up to 3->4 now, and would go 4->5 if I were to do
> it again ...

That definitely sounds like VACUUM thinks there's an old open transaction
somewhere and so it doesn't want to clean out the dead tuples.

I believe we have a mechanism for deciding that an old transaction must
have aborted (it involves looking to see if any active backend claims to
be running that transaction).  But I wonder whether that mechanism is
being used when VACUUM decides whether it can clean out a dead tuple or
not.  Vadim?

> Don't know ... one of hte problems I'm having with my FreeBSD machine
> right now is that, for some reason, setproctitle() isn't working, so all
> my backends look the same 'postmaster' and its start up options :(  

Now you know how the other half lives ;-).
        regards, tom lane