>>The only other job that could be running is a vacuum I run at 1am but I
don't think it would take an hour to run.
Famous last words... :-) It should be easy to check this, but I don't know
if that is a likely source of problems anyway.
If I were you I'd just do VACUUM ANALYSE in one comand. It
"David Witham" <[EMAIL PROTECTED]> writes:
> Occasionally I get this error message from the analyze job:
> ERROR: simple_heap_update: tuple concurrently updated
> What does this mean and should I do anything about it?
You can get this if two ANALYZEs run in parallel for the same table;
whichever
Hi all,
I run a cron job at 2am every night to do an ANALYZE on my whole database:
su - postgres -c 'echo analyze | /usr/bin/psql buns | grep -v ANALYZE'
Its a batch oriented database so there is no user activity on it at this time. The
only other job that could be running is a vacuum I run at
