Skip site navigation (1) Skip section navigation (2)

Re: Data corruption after SAN snapshot

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Terry Schmitt <tschmitt(at)schmittworks(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Data corruption after SAN snapshot
Date: 2012-08-07 23:01:09
Message-ID: CA+U5nMLEe6uyxwbw6qGTEwbrTeUBUWHAi5VLxJ-HAswTLWjfAw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On 7 August 2012 23:23, Terry Schmitt <tschmitt(at)schmittworks(dot)com> wrote:

> I have a pretty strange issue that I'm looking for ideas on.
> I'm using Postgres Plus Advanced Server 9.1, but I believe this problem is
> relevant to Postgres Community. It is certainly possible to be a EDB bug and
> I am already working with them on this.

I think its important to say that as soon as someone patches/forks
Postgres code then the onus is really on whoever did that to show the
problem wasn't created by them when they did that. That is very much
the reason why my company and many others don't market a forked
product and stick closely to the community distributed binaries.

I have much respect for your vendors ability to diagnose faults and
recreate them on stock Postgres if appropriate, so I think we should
wait for that to happen rather than attempt to answer this just yet.
Or alternatively, please submit a test case that fails on Postgres if
you doubt that.

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

pgsql-admin by date

Next:From: Terry SchmittDate: 2012-08-07 23:18:00
Subject: Re: Data corruption after SAN snapshot
Previous:From: Terry SchmittDate: 2012-08-07 22:23:33
Subject: Data corruption after SAN snapshot

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group