Re: database must be vacuumed with <N> transactions

From: Dave Johansen <davejohansen(at)gmail(dot)com>
To: John Scalia <jayknowsunix(at)gmail(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: database must be vacuumed with <N> transactions
Date: 2015-06-25 18:42:02
Message-ID: CAAcYxUfZorpYKo42v-+bW_x=UqT3JEUtUKJ4wPieH8nFsUM-xA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Jun 25, 2015 at 11:38 AM, John Scalia <jayknowsunix(at)gmail(dot)com>
wrote:

> The pg_stat_activity table will show you which processes are doing what,
> and you'll be able to see their process ID from the O/S. That might help
> you.
>

Yes, but I need to see which process ID is doing a TON of small
transactions which is causing the XID to increment at an unexpectedly high
rate and so my question is "if there's a way for me to get the XID for
every connection/query?".

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message John Scalia 2015-06-25 18:42:47 Re: database must be vacuumed with <N> transactions
Previous Message John Scalia 2015-06-25 18:38:10 Re: database must be vacuumed with <N> transactions