| From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
|---|---|
| To: | Dave Johansen <davejohansen(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:47 |
| Message-ID: | CABzCKRAD21ZzrKjpQM6AL0ycjJf5DMyV=1=8f0G8i2OO1RHM5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Logging?
On Thu, Jun 25, 2015 at 11:42 AM, Dave Johansen <davejohansen(at)gmail(dot)com>
wrote:
> 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?".
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keith | 2015-06-25 21:23:44 | Re: database must be vacuumed with <N> transactions |
| Previous Message | Dave Johansen | 2015-06-25 18:42:02 | Re: database must be vacuumed with <N> transactions |