On Fri, Aug 2, 2013 at 12:51 AM, Klaus Ita wrote:
> Isn't it a funny coincidence, that we also had a corruption of that
> same/similar type?
>
> my disk was quite confidently not tampered. I am wondering: Does PG sign, or
> checksum wal_files? Is the integrity of wal_files ensured by any mechanism
Isn't it a funny coincidence, that we also had a corruption of that
same/similar type?
my disk was quite confidently not tampered. I am wondering: Does PG sign,
or checksum wal_files? Is the integrity of wal_files ensured by any
mechanism? Because if it IS, then - in our case - it's a corruption c
On Tue, Jul 30, 2013 at 9:28 PM, Andres Freund wrote:
> Any chance you could https://github.com/snaga/xlogdump that and the
> neighbouring segments? That might tell us whether we're dealing with
> broken locking or possibly disk corruption (doesn't sound too likely).
>
Actually, we did find what
On 2013-07-31 01:27:39 +, mac...@heroku.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8347
> Logged by: Maciek Sakrejda
> Email address: mac...@heroku.com
> PostgreSQL version: 9.2.4
> Operating system: Ubuntu 12.04.2 LTS 64-bit
> Descri
The following bug has been logged on the website:
Bug reference: 8347
Logged by: Maciek Sakrejda
Email address: mac...@heroku.com
PostgreSQL version: 9.2.4
Operating system: Ubuntu 12.04.2 LTS 64-bit
Description:
Running into a recovery failure on a customer's replica
