| From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: [SQL] pg_multixact issues |
| Date: | 2014-09-17 20:36:46 |
| Message-ID: | CALSLE1MAgy4QC0-xLju6MBxO6Upp6=84xwAMt2dkfiGbd6pB9Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
On Wed, Sep 17, 2014 at 7:20 PM, Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> wrote:
> On Wed, Sep 17, 2014 at 6:51 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
> wrote:
>
>>
>> http://www.postgresql.org/docs/9.3/static/routine-
>> vacuuming.html#VACUUM-FOR-MULTIXACT-WRAPAROUND
>>
>
Looked into these details. Can there be an example explained that will
really help to understand this in practice?
Also one additional information here, the database was restarted various
times. But still the pg_multixact directory size is increasing.
Actually there were multiple updates happening in different processes which
lead to the locking issues and landed up into this situation.
How can I recover the system at this stage and also clean up pg_multixact
gracefully?
Regards...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-09-17 20:47:40 | Re: Regarding timezone |
| Previous Message | Dev Kumkar | 2014-09-17 20:14:05 | Re: Regarding timezone |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-09-17 20:41:26 | Re: Collations and Replication; Next Steps |
| Previous Message | Pavel Stehule | 2014-09-17 20:17:22 | Re: Anonymous code block with parameters |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-09-17 21:08:59 | Re: pg_multixact issues |
| Previous Message | Dev Kumkar | 2014-09-17 14:54:42 | Re: [SQL] pg_multixact issues |