Armand du Plessis wrote:
> We're running into a scenario where despite doing a manual vacuum as a
> superuser the relfrozenxid for
> one relation now dangerously close to wraparound is not getting reset.
>
> It's a Postgres 9.2.3 cluster. We shutdown other access to the machine while
> running t
Brian Wong wrote:
> After upgrading postgresql from 9.1.1 to 9.1.9, launching pgadmin3's server
> status window gives an
> error dialog box. This is a pgadmin3 client on Windows. The error says:
>
> --
> An error has occurred:
> ERROR:
Thanks a lot Albe, Gezeala.
I missed the 701995 dead rows cannot be removed yet in the logs (was late)
and will now know to check the toast tables as well if this happens again.
Thank you!
Armand
On Tue, Aug 6, 2013 at 9:04 AM, Albe Laurenz wrote:
> Armand du Plessis wrote:
> > We're running
I meant I went into there with psql and was able to see the adminpack's
objects.
I checked the location of the Postgresql server
software(/opt/Postgresql/9.1.9/lib) and couldn't find adminpack.so. On a
server for which there's no such an error, I see the same files and those 2
files aren't there
Brian Wong wrote:
>>> After upgrading postgresql from 9.1.1 to 9.1.9, launching pgadmin3's server
>>> status window gives an
>>> error dialog box. This is a pgadmin3 client on Windows. The error says:
>>>
>>> --
>>> An error has occurre
