pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: Haribabu Kommi <kommi.haribabu@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Per table autovacuum vacuum cost limit behaviour strange
Date: Fri, 3 Oct 2014 13:06:33 -0300
Message-ID: <20141003160632.GC7043@eldon.alvh.no-ip.org> (raw)
In-Reply-To: <20141003003526.GE28859@tamriel.snowman.net>
References: <53686F22.8030300@catalyst.net.nz>
	<20140826161911.GE6343@eldon.alvh.no-ip.org>
	<CA+Tgmoav37msTP0pVsrEYz4LBYU6SETMZGYTgPo5AEOC0yCMbA@mail.gmail.com>
	<20140930221644.GR5311@eldon.alvh.no-ip.org>
	<20141002135412.GX5311@eldon.alvh.no-ip.org>
	<CA+TgmobQokthgWmv1C9vjvpz=K9koovy6O+nWZ9rV8gwC8ioRw@mail.gmail.com>
	<20141002150336.GO28859@tamriel.snowman.net>
	<20141002153705.GY5311@eldon.alvh.no-ip.org>
	<20141002215950.GB5311@eldon.alvh.no-ip.org>
	<20141003003526.GE28859@tamriel.snowman.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Stephen Frost wrote:
> * Alvaro Herrera (alvherre@2ndquadrant.com) wrote:

> > I am rather surprised that nobody has reported this problem before.  I
> > am now of the mind that this is clearly a bug that should be fixed all
> > the way back.
> 
> I'm coming around to that also, however, should we worry about users who
> set per-table settings and then simply forgot about them?  I suppose
> that won't matter too much unless the table is really active, and if it
> is, they've probably already set it to zero.

Right.

For the cases where it's been set and forgotten, perhaps we can have an
item in release notes to tell people to look into tables with the
parameters set in pg_class.reloptions (to any value different from zero)
and to look for performance differences from previous versions when they
are.

I have pushed this now, backpatch all the way back to 9.0.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


-- 
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 (40+ messages)

Message-ID: <20141003160632.GC7043@eldon.alvh.no-ip.org>
Permalink:  ../20141003160632.GC7043@eldon.alvh.no-ip.org/
Also on:    postgresql.org/message-id/20141003160632.GC7043@eldon.alvh.no-ip.org

 · 

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-hackers@postgresql.org
  Cc: alvherre@2ndquadrant.com, sfrost@snowman.net, robertmhaas@gmail.com, mark.kirkwood@catalyst.net.nz, amit.kapila16@gmail.com, kommi.haribabu@gmail.com
  Subject: Re: Per table autovacuum vacuum cost limit behaviour strange
  In-Reply-To: <20141003160632.GC7043@eldon.alvh.no-ip.org>

* 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