pg.ddx.io pgsql-admin@postgresql.org mailing list archive help / color / mirror / Atom feed From: Pavan Deolasee <pavan.deolasee@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Cédric Villemain <cedric.villemain.debian@gmail.com>
Cc: Greg Stark <gsstark@mit.edu>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Florian Helmberger <fh@25th-floor.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum
Date: Sun, 29 May 2011 22:49:00 +0530
Message-ID: <BANLkTi=9RZPv9JOjRdSX6imBeSBGLLrCPA@mail.gmail.com> (raw )
In-Reply-To: <22525.1306688753@sss.pgh.pa.us >
References: <4DD28F73.6010108@25th-floor.com >
<25017.1306291669@sss.pgh.pa.us >
<4DDCA801.70805@25th-floor.com >
<19738.1306338472@sss.pgh.pa.us >
<BANLkTi=973Arh-nXLO6YFP7_ZTCeNp-X7w@mail.gmail.com >
<22497.1306341699@sss.pgh.pa.us >
<BANLkTi=jcKSU5zR+JG2BvfLNCtezC9sb+g@mail.gmail.com >
<15043.1306423500@sss.pgh.pa.us >
<BANLkTikrCaoZCVrda6SNCUQFiYvvZX75BA@mail.gmail.com >
<25097.1306426982@sss.pgh.pa.us >
<BANLkTikxM6V5DUsXnDEs84z=oRMbyeoOgA@mail.gmail.com >
<4DDE475B020000250003DD63@gw.wicourts.gov >
<BANLkTikTbZ8gibj+X++vkdqkxxJCU6trWw@mail.gmail.com >
<4DDE5033020000250003DD71@gw.wicourts.gov >
<BANLkTikGu30z1rwYeN0NwuO8jMFWHzus+Q@mail.gmail.com >
<4DDE7EB8020000250003DDA8@gw.wicourts.gov >
<9007.1306446600@sss.pgh.pa.us >
<BANLkTinREie2cX2zqZPSEfUsZsdM+GjymQ@mail.gmail.com >
<28116.1306609295@sss.pgh.pa.us >
<BANLkTi=6RYvEVfKn8ufPEf9meGVEu=fHsQ@mail.gmail.com >
<11295.1306645848@sss.pgh.pa.us >
<BANLkTimbSiUZC7+ZZJOzMWp=M2jYZZcJSg@mail.gmail.com >
<19876.1306680027@sss.pgh.pa.us >
<BANLkTimTJLzdPDHrVUa=56n_mPtPtO3D3w@mail.gmail.com >
<22525.1306688753@sss.pgh.pa.us >
On Sun, May 29, 2011 at 10:35 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Pavan Deolasee <pavan.deolasee@gmail.com> writes:
>> I am sorry if I sounded terse above. But my gripe is that sometimes we
>> are too reluctant to listen to ideas and insist on producing some hard
>> numbers first which might take significant efforts. But we are not
>> equally strict when such changes are introduced initially.
>
> The reason for not wanting to change it without some actual evidence
> is that there is already evidence: the code has been in the field with
> this setting since 8.4, and nobody's vacuum performance has fallen off a
> cliff.
Well, that's probably because there was definitely much improvement
over what existed before. But that does not mean we can't make it
better. IOW there are no complaints because there is no regression.
> So while I'd agree that there was little testing done before the
> code went in, there is more than zero reason to leave it where it is.
> Without some positive evidence showing that another value is better,
> I'm disinclined to change it. I also think that you're not helping
> by complaining about the code without being willing to do some work
> to try to collect such evidence.
>
I am not complaining about the code. I am suggesting we can be more
receptive to ideas, especially when we know what we have today was not
backed by any evidence either. I will anyways do some tests and post
numbers when I work on single-pass vacuum patch. I'll try to
experiment with this stuff at that time.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
view thread (48+ messages) latest in thread
Message-ID: <BANLkTi=9RZPv9JOjRdSX6imBeSBGLLrCPA@mail.gmail.com>
Permalink: ../BANLkTi=9RZPv9JOjRdSX6imBeSBGLLrCPA@mail.gmail.com/
Also on: postgresql.org/message-id/BANLkTi=9RZPv9JOjRdSX6imBeSBGLLrCPA@mail.gmail.com
copy link · copy postgr.es
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: pavan.deolasee@gmail.com, tgl@sss.pgh.pa.us, cedric.villemain.debian@gmail.com, gsstark@mit.edu, robertmhaas@gmail.com, Kevin.Grittner@wicourts.gov, fh@25th-floor.com, alvherre@commandprompt.com, pgsql-hackers@postgresql.org
Subject: Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum
In-Reply-To: <BANLkTi=9RZPv9JOjRdSX6imBeSBGLLrCPA@mail.gmail.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