On Fri, Aug 11, 2017 at 1:33 PM, Greg Stark wrote:
> On 10 August 2017 at 15:26, Chris Travers wrote:
> >
> >
> > The bitwise comparison is interesting. Remember the error was:
> >
> > pg_xlogdump: FATAL: error in WAL record at 1E39C/E1117FB8: unexpected
> > pageaddr 1E375/61118000 in log segm
On Fri, Aug 11, 2017 at 1:33 PM, Greg Stark wrote:
> On 10 August 2017 at 15:26, Chris Travers wrote:
> >
> >
> > The bitwise comparison is interesting. Remember the error was:
> >
> > pg_xlogdump: FATAL: error in WAL record at 1E39C/E1117FB8: unexpected
> > pageaddr 1E375/61118000 in log segm
On 10 August 2017 at 15:26, Chris Travers wrote:
>
>
> The bitwise comparison is interesting. Remember the error was:
>
> pg_xlogdump: FATAL: error in WAL record at 1E39C/E1117FB8: unexpected
> pageaddr 1E375/61118000 in log segment 0001E39C00E1, offset
> 1146880
...
> Since this did
On Thu, Aug 10, 2017 at 3:17 PM, Vladimir Rusinov
wrote:
>
>
> On Thu, Aug 10, 2017 at 1:48 PM, Aleksander Alekseev <
> a.aleks...@postgrespro.ru> wrote:
>
>> I just wanted to point out that a hardware issue or third party software
>> issues (bugs in FS, software RAID, ...) could not be fully exc
On Thu, Aug 10, 2017 at 1:48 PM, Aleksander Alekseev <
a.aleks...@postgrespro.ru> wrote:
> I just wanted to point out that a hardware issue or third party software
> issues (bugs in FS, software RAID, ...) could not be fully excluded from
> the list of suspects. According to the talk by Christophe
Hi Chris,
> I ran into a funny situation today regarding PostgreSQL replication and
> wal corruption and wanted to go over what I think happened and what I
> wonder about as a possible solution.
Sad story. Unfortunately I have no idea what could be a reason nor can I
suggest a good way to find it
> Yes. Exactly the same output until a certain point where pg_xlogdump dies
> with an error. That is the same LSN where PostgreSQL died with an error on
> restart.
>
One other thing that is possibly relevant after reading through the last
bug report is the error pgxlogdumo gives:
pg_xlogdump:
Sorry, meant to reply all.
On Thu, Aug 10, 2017 at 2:19 PM, Vladimir Borodin wrote:
> Hi, Chris.
>
> 10 авг. 2017 г., в 15:09, Chris Travers
> написал(а):
>
> Hi;
>
> I ran into a funny situation today regarding PostgreSQL replication and
> wal corruption and wanted to go over what I think happ
Hi, Chris.
> 10 авг. 2017 г., в 15:09, Chris Travers написал(а):
>
> Hi;
>
> I ran into a funny situation today regarding PostgreSQL replication and wal
> corruption and wanted to go over what I think happened and what I wonder
> about as a possible solution.
>
> Basic information is custom-
