Re: DATA corruption after promoting slave to master

From: Shaun Thomas <sthomas(at)optionshouse(dot)com>
To: 'Kirit Parmar' <kirit(dot)p(at)directi(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, "Karthik Iyer" <karthik(dot)i(at)directi(dot)com>, Reinwald Warapen <reinwald(dot)w(at)directi(dot)com>
Subject: Re: DATA corruption after promoting slave to master
Date: 2014-11-07 17:58:38
Message-ID: 0683F5F5A5C7FE419A752A034B4A0B9797DA283A@sswchi5pmbx2.peak6.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Krit,

It sounds like you might be hitting edge-case statistics problems on recent data. We've had issues with this before, ourselves. I'd personally recommend increasing your default_statistics_target to 400 for your entire database in general. But it's possible that won't help this. Recent data tends to have no stats at all, and if it comes in with enough volume, the planner will be wrong a good majority of the time. If that's the data you're trying to grab, well...

Based on that, you might want to consider tweaking your autovacuum_analyze_scale_factor setting so you get relatively frequent automatic analyzes so the stats are better through the day. Otherwise, your approach should work just fine.

Good luck!

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email

In response to

Browse pgsql-general by date

  From Date Subject
Next Message harpagornis 2014-11-09 04:07:47 SSL Certificates in Postgres 9.3 and Windows 7
Previous Message Devrim Gündüz 2014-11-07 17:43:54 Re: Testing on Power 8 systems