pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: hydra <hydrapolic@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: replication consistency checking
Date: Thu, 11 Jun 2015 08:53:16 -0400
Message-ID: <20150611125316.GA14868@momjian.us> (raw)
In-Reply-To: <20150611123904.GA19473@momjian.us>
References: <CAL_0b1s9ZE1=ZRVySGE-Q3jLJC4U_O1y_PzN-R1vUbnNb7hKhg@mail.gmail.com>
	<CAG6MAzRW57SFsYXXBi213FK1yKrgOcprkxfHEib6+1pLyO6YVA@mail.gmail.com>
	<A76B25F2823E954C9E45E32FA49D70ECCD45F1BC@mail.corp.perceptron.com>
	<CAG6MAzQNQPRSsRL6629id-5i2jv6AQZ0y25=YYU2M3CJAOCiTg@mail.gmail.com>
	<A76B25F2823E954C9E45E32FA49D70ECCD45F26C@mail.corp.perceptron.com>
	<D9E31A4B-66EB-426D-A418-2C29578E305E@elevated-dev.com>
	<CAG6MAzRDu93nphAt9wrZb-kRYm2N7TCL1-_PYpMkiC4LvVn9zg@mail.gmail.com>
	<A957CFF5-05C5-4CD5-8CD6-404B7F0F1BF2@web.de>
	<CAG6MAzRjcwxDjGE65O3AiHX0k9Dve9PsX7Qigei_=Mc1OnO38w@mail.gmail.com>
	<20150611123904.GA19473@momjian.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

On Thu, Jun 11, 2015 at 08:39:05AM -0400, Bruce Momjian wrote:
> On Thu, Jun 11, 2015 at 07:12:36AM +0200, hydra wrote:
> >     I am entering this discussion a bit late, so maybe I am missing the point.
> >     But SR is using xlog and there is a crc32 checksum on each xlog record. So
> >     why would you need to compare the whole thing again when each record has
> >     been approved during replication ?
> > 
> > 
> > 
> > Hello Jan,
> > you don't have it if you don't want to. However I'd like to have the
> > possibility to do so and thus I was asking - is it possible? Are you guys doing
> > it?
> > 
> > The reasons are mentioned above, but still:
> > - bugs can appear anywhere,
> > - the bug report mentioned before also states to check the data, but does not
> > give and hints how to do it, that's why I asked here
> 
> The answer is "no".

You are falling into a trap I see often.  There is a flaw in another
database product, and you want Postgres to fix it or monitor for it.
Postgres just doesn't have that problem to the same level.  We have
different problems, and we allocate resources to add features based on
our own problems, not the problems of other database products.
  
-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (34+ messages)  latest in thread

Message-ID: <20150611125316.GA14868@momjian.us>
Permalink:  ../20150611125316.GA14868@momjian.us/
Also on:    postgresql.org/message-id/20150611125316.GA14868@momjian.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: bruce@momjian.us, hydrapolic@gmail.com
  Subject: Re: replication consistency checking
  In-Reply-To: <20150611125316.GA14868@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox