Tom,
I am not sure exactly what you mean by 'open client transactions' but I
just killed off all client processes. The only postgres processes
running are:
[root@cvs root]# ps -ef | grep post
postgres 1004 1 0 Jul03 ? 00:00:00
/usr/local/pgsql/bin/postmaster
postgres 1069 1004 0 Jul03 ? 00:00:00 postgres: stats buffer
process
postgres 1070 1069 0 Jul03 ? 00:00:00 postgres: stats
collector proces
I then reconnected via psql and reran the vacuum full getting the same
error.
--Barry
Tom Lane wrote:
>Barry Lind <barry@xythos.com> writes:
>
>
>>It was not compiled with debug. I will do that now and see if this
>>happens again in the future. If and when it happens again what would
>>you like me to do? I am willing provide you access if you need it.
>>
>>
>
>Well, first off, please confirm that killing off open client
>transactions (you shouldn't even need to do a full postmaster restart)
>makes the problem go away.
>
>Beyond that, I have no advice except to be prepared to apply a debugger
>next time. I believe we could fix the problem if we could examine the
>situation VACUUM is seeing --- but it's so far not been possible to
>do that, because the triggering conditions are so transient.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 5: Have you checked our extensive FAQ?
>
>http://www.postgresql.org/users-lounge/docs/faq.html
>
>
>
