Re: [HACKERS] ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound after missused pg_resetxlogs

2017-10-31 Thread Robert Haas
On Mon, Oct 16, 2017 at 5:41 PM, alain radix wrote: > I’m facing a problem with a PostgreSQL 9.6.2 reporting this error when > selecting a table > > ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound > > The root cause is not a Postgres bug but a buggy person that used > p

Re: [HACKERS] ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound after missused pg_resetxlogs

2017-10-16 Thread Alvaro Herrera
RADIX Alain - externe wrote: > I'm facing a problem with a PostgreSQL 9.6.2 reporting this error when > selecting a table > ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound > > The root cause is not a Postgres bug but a buggy person that used > pg_resetxlogs obviously

[HACKERS] ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound after missused pg_resetxlogs

2017-10-16 Thread RADIX Alain - externe
Hi, I'm facing a problem with a PostgreSQL 9.6.2 reporting this error when selecting a table ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound The root cause is not a Postgres bug but a buggy person that used pg_resetxlogs obviously without reading or understanding the

[HACKERS] ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound after missused pg_resetxlogs

2017-10-16 Thread alain radix
Hi, I’m facing a problem with a PostgreSQL 9.6.2 reporting this error when selecting a table ERROR: MultiXactId 3268957 has not been created yet -- apparent wraparound The root cause is not a Postgres bug but a buggy person that used pg_resetxlogs obviously without reading or understanding