Tom Lane a écrit :
Jean-Christophe Praud 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.
How
Jean-Christophe Praud 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.
> How can I get rid of these
Tom Lane a écrit :
Jean-Christophe Praud 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 with top and
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
Jean-Christophe Praud 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 with top and iotop, I see the process takes
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, I see the
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 duri
