From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ray Stell <stellr@vt.edu>
cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: 9.0.15 WAL mis-replay status?
In-reply-to: <8D8B1117-25D3-4C82-9FB5-6CE5C8E2C3EC@vt.edu>
References: <8D8B1117-25D3-4C82-9FB5-6CE5C8E2C3EC@vt.edu>
Comments: In-reply-to Ray Stell <stellr@vt.edu>
 message dated "Mon, 28 Apr 2014 10:18:28 -0400"
Date: Mon, 28 Apr 2014 11:07:22 -0400
Message-ID: <12664.1398697642@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Ray Stell <stellr@vt.edu> writes:
> I finally got permission to patch a highly used db from 9.0.15 to .17.  Is there any way to know if the WAL replay issue has effected the standby?  I don't have the reported bloat, is that THE test?  Is there any way to measure the current state of this issue listed in the 9.0.16 release notes:
> Fix possible mis-replay of WAL records when some segments of a relation aren't full size (Greg Stark, Tom Lane)

TBH, I'd suggest re-syncing the standby after you upgrade.  Obvious bloat
is one symptom, but only one symptom.

Note however that the issue could only arise on tables that exceed 1GB, so
depending on your usage, maybe you don't have a problem.

			regards, tom lane


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