| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ray Stell <stellr(at)vt(dot)edu> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: 9.0.15 WAL mis-replay status? |
| Date: | 2014-04-28 15:07:22 |
| Message-ID: | 12664.1398697642@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Ray Stell <stellr(at)vt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ray Stell | 2014-04-28 19:41:23 | Re: 9.0.15 WAL mis-replay status? |
| Previous Message | Ray Stell | 2014-04-28 14:18:28 | 9.0.15 WAL mis-replay status? |