On further review this particular server skipped from 9.2.2 to 9.2.4. This is my most busy and downtime sensitive server and I was waiting on a maintenance window to patch to 9.2.3 when 9.2.4 dropped and bumped up the urgency. However, I have 3 other less busy production servers that were all running 9.2.3 for a while, didnt exhibit the problem, and still dont on 9.2.4.
psql> analyze seems to work ok in the meantime, I'll report back if I notice any problems with that.
Thanks very much for the response and investigation, it is much appreciated!
On Thu, Apr 11, 2013 at 8:48 PM, Kevin Grittner <kgrittn@xxxxxxxxx> wrote:
Tom Lane <tgl@xxxxxxxxxxxxx> wrote:I'm pretty sure that nobody involved noticed the impact on VACUUM
> However I've got to say that both of those side-effects of
> exclusive-lock abandonment seem absolutely brain dead now that I
> see them. Why would we not bother to tell the stats collector
> what we've done? Why would we think we should not do ANALYZE
> when we were told to?
>
> Would someone care to step forward and defend this behavior?
> Because it's not going to be there very long otherwise.
ANALYZE command; all discussion was around autovacuum impact; and
Jan argued that this was leaving things in a status quo for that,
so I conceded the point and left it for a follow-on patch if
someone felt the behavior needed to change. Sorry for the miss.
http://www.postgresql.org/message-id/50BB700E.8060404@xxxxxxxxx
As far as I'm concerned all effects on the explicit command were
unintended and should be reverted.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
