From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Tiffany Thang <tiffanythang(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Forums postgresql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_multixact/members growing |
Date: | 2018-05-23 22:37:38 |
Message-ID: | 20180523223738.jt6bhksace23o3js@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2018-May-23, Tom Lane wrote:
> Tiffany Thang <tiffanythang(at)gmail(dot)com> writes:
> > Where do I find pg_controldata? I could not locate it on the file system.
>
> Hmm, should be one of the installed PG executables.
>
> > pg_clog/ or pg_subtrans/ or pg_multixact/offsets/ are getting larger too
> > but by only a few hundreds MBs.
>
> This is consistent with the idea that something is holding back the
> oldest-transaction horizon. (However, I'd think you'd also be having
> serious problems with table bloat if that were true, so it's a bit
> mystifying.) Did you check for unclosed prepared transactions?
Another option is that you have a standby server with
hot_standby_feedback enabled, and an open transaction there. I'm not
sure to what extent it is possible for that to cause multixact problems,
but it wouldn't hurt to check.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Ben Chobot | 2018-05-23 23:36:37 | Re: Renice on Postgresql process |
Previous Message | Tom Lane | 2018-05-23 22:16:21 | Re: pg_multixact/members growing |