Hi all,
I've a problem on a heavy loaded database: vacuums don't work since
about a week. All I got is:
mybase=# vacuum verbose analyze public.mytable;
INFO: vacuuming public.mytable
(I stop it after hours)
Looking with top and iotop, I see the process takes some cpu and disk io
time
Alvaro Herrera a écrit :
Jean-Christophe Praud wrote:
Hi all,
I've a problem on a heavy loaded database: vacuums don't work since
about a week. All I got is:
mybase=# vacuum verbose analyze public.mytable;
INFO: vacuuming public.mytable
(I stop it after hours)
Looking with top and iotop
Tom Lane a écrit :
Jean-Christophe Praud j...@steek.com writes:
I've a problem on a heavy loaded database: vacuums don't work since
about a week. All I got is:
mybase=# vacuum verbose analyze public.mytable;
INFO: vacuuming public.mytable
(I stop it after hours)
Looking
Tom Lane a écrit :
Jean-Christophe Praud j...@steek.com writes:
Indeed, the tables I tried to vacuum have locks on them.
AccessShareLock belonging to queries which seem sleeping. I tried to
kill these queries but pg_cancel_backend() has no effect, and the
process doesn't get the 15 signal
not to
block the client application during the recursive process ?
Regards,
--
Jean-Christophe Praud - http://shub-niggurath.com
Conseil Développement Informatique http://www.praud.com
Ph'nglui mglw'nafh Cthulhu n'gah Bill R'lyeh Wgah'nagl fhtagn
