pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <kgrittn@ymail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Mike Broers <mbroers@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: Jan Wieck <JanWieck@Yahoo.com>
Subject: Re: [ADMIN] after 9.2.4 patch vacuumdb -avz not analyzing all tables
Date: Thu, 11 Apr 2013 18:48:02 -0700 (PDT)
Message-ID: <1365731282.15026.YahooMailNeo@web162905.mail.bf1.yahoo.com> (raw)
In-Reply-To: <28473.1365724754@sss.pgh.pa.us>
References: <CAB9893het38CbHoHOt=GZ5tuUnb77EauGidjHsyy7Mqu_4_P9w@mail.gmail.com>
	<28473.1365724754@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Tom Lane <tgl@sss.pgh.pa.us> wrote:

> 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.

I'm pretty sure that nobody involved noticed the impact on VACUUM
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@Yahoo.com

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


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



view thread (9+ messages)  latest in thread

Message-ID: <1365731282.15026.YahooMailNeo@web162905.mail.bf1.yahoo.com>
Permalink:  ../1365731282.15026.YahooMailNeo@web162905.mail.bf1.yahoo.com/
Also on:    postgresql.org/message-id/1365731282.15026.YahooMailNeo@web162905.mail.bf1.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: kgrittn@ymail.com, tgl@sss.pgh.pa.us, mbroers@gmail.com, pgsql-hackers@postgresql.org, JanWieck@Yahoo.com
  Subject: Re: [ADMIN] after 9.2.4 patch vacuumdb -avz not analyzing all tables
  In-Reply-To: <1365731282.15026.YahooMailNeo@web162905.mail.bf1.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox