Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z31yz-0006U5-1N for pgsql-admin@arkaria.postgresql.org; Thu, 11 Jun 2015 12:53:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Z31yy-0002YI-EA for pgsql-admin@arkaria.postgresql.org; Thu, 11 Jun 2015 12:53:20 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Z31yx-0002YC-LN for pgsql-admin@postgresql.org; Thu, 11 Jun 2015 12:53:19 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Z31yu-0008EC-Pd for pgsql-admin@postgresql.org; Thu, 11 Jun 2015 12:53:18 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1Z31yu-00044P-1i; Thu, 11 Jun 2015 08:53:16 -0400 Date: Thu, 11 Jun 2015 08:53:16 -0400 From: Bruce Momjian To: hydra Cc: pgsql-admin Subject: Re: replication consistency checking Message-ID: <20150611125316.GA14868@momjian.us> References: <20150611123904.GA19473@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150611123904.GA19473@momjian.us> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org 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 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