| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | molofeev <molofeev3(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5 |
| Date: | 2018-04-03 13:23:19 |
| Message-ID: | 20180403132319.e2wtdc26ks54qbqt@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
molofeev wrote:
> Thank you for reply.
> Output of pg_controldata:
>
> Latest checkpoint's NextMultiXactId: 1
> Latest checkpoint's NextMultiOffset: 0
Uh, this says that this cluster has never used any multixacts.
> Output of [select datminmxid from pg_database where datname =
> current_database();]:
>
> datminmxid
> ------------
> 1
... and this confirms.
I think the easiest way forward is to identify the problem page and see
what's there. Please find what command was being run that caused the
error, which might help narrow down which table it is; then scan the
table to see on which page you can see the error.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | molofeev | 2018-04-03 13:36:45 | Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5 |
| Previous Message | molofeev | 2018-04-03 13:17:58 | Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5 |