Re: autovaccum task got cancelled

From: bricklen <bricklen(at)gmail(dot)com>
To: Gary Fu <gfu(at)sigmaspace(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: autovaccum task got cancelled
Date: 2013-10-31 21:50:34
Message-ID: CAGrpgQ9bHzfrCwzbzj0msUiU+LOd+7qXFYuoLgjstD8GQ8-VVg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 31, 2013 at 11:51 AM, Gary Fu <gfu(at)sigmaspace(dot)com> wrote:

> Hello,
>
> I'm running an application (with programs in Perl) through pgpool 3.1 with
> replication mode to two postgresql db servers (version 9.0.13). Recently,
> I noticed that the following messages repeatedly showed in postgres log
> files. As far as I know, the application programs do not make any specific
> lock on the 'file' table. I'm not sure if it is caused by the pgpool or
> something else.
>

Try setting your log_line_prefix so that more details are logged, that
might help track down where the locks etc are coming from.
Eg
log_line_prefix = '%m [%p] (user=%u) (db=%d) (rhost=%h) [vxid:%v txid:%x]
[%i] '

and reload your config (eg. "select pg_reload_conf()" as the superuser)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message john gale 2013-10-31 22:46:48 Hstore::TooBig ?
Previous Message andy 2013-10-31 20:31:41 Re: Connection pooling