Re: database must be vacuumed with transactions - Mailing list pgsql-admin

From Dave Johansen
Subject Re: database must be vacuumed with transactions
Date
Msg-id CAAcYxUfZorpYKo42v-+bW_x=UqT3JEUtUKJ4wPieH8nFsUM-xA@mail.gmail.com
Whole thread Raw
In response to Re: database must be vacuumed with transactions  (John Scalia <jayknowsunix@gmail.com>)
Responses Re: database must be vacuumed with transactions  (John Scalia <jayknowsunix@gmail.com>)
Re: database must be vacuumed with transactions  (Keith <keith@keithf4.com>)
List pgsql-admin
On Thu, Jun 25, 2015 at 11:38 AM, John Scalia <jayknowsunix@gmail.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?".

pgsql-admin by date:

Previous
From: John Scalia
Date:
Subject: Re: database must be vacuumed with transactions
Next
From: John Scalia
Date:
Subject: Re: database must be vacuumed with transactions