Re: BUG #8673: Could not open file "pg_multixact/members/xxxx" on slave during hot_standby

From: Serge Negodyuck <petr(at)petrovich(dot)kiev(dot)ua>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8673: Could not open file "pg_multixact/members/xxxx" on slave during hot_standby
Date: 2013-12-10 13:22:49
Message-ID: CABKyZDEG=caaPEPy3jFMYvB=x0pOaeMZ9FL96eaPLPjnny1BzQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

> From both members, and offset. I'd be great if you could attach a ls -lR
> of pg_multixact/.
>

I've set up another slave (in not production mode) to reproduce this
bug and provide more details if necessary.
There are no "apparent wraparound" message in logs yet. Probably
because I cannot sent the same SQL queries to non-production server.

Just to provide exact information: these are links to ls -lR
pg_multixact/ of both master and slave server.

https://drive.google.com/file/d/0B5sVzeuionyGVER6dnA3a0NkOU0/
https://drive.google.com/file/d/0B5sVzeuionyGUlFibC1jZEVvQzA/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Maciek Sakrejda 2013-12-10 17:36:04 Re: BUG #8656: Duplicate data violating unique constraints
Previous Message Alvaro Herrera 2013-12-10 04:25:20 Re: BUG #8673: Could not open file "pg_multixact/members/xxxx" on slave during hot_standby

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2013-12-10 13:55:58 Re: Optimize kernel readahead using buffer access strategy
Previous Message Andres Freund 2013-12-10 11:18:22 Re: tracking commit timestamps