From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Royce Ausburn <royce(dot)ml(at)inomial(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: [PATCH] Unremovable tuple monitoring (was: Addition of some trivial auto vacuum logging) |
Date: | 2011-10-04 12:26:32 |
Message-ID: | CA+TgmobsYcYwHs=uM6jnwHq6OiK3oXmcjHRhvcy9zCyukUxqmg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Oct 3, 2011 at 9:17 AM, Royce Ausburn <royce(dot)ml(at)inomial(dot)com> wrote:
> - I'm not sure if I'm supposed to update CATALOG_VERSION_NO in catalog.h. In this patch I have.
Generally that is left to the committer, as the correct value depends
on the value at the time of commit, not the time you submit the patch;
and including it in the patch tends to result in failing hunks, since
the value changes fairly frequently.
> - I'm not sure about how I should be selecting an OID for my new stats function. I used the unused_oids script and picked one that seemed reasonable.
That's the way to do it.
> - The VACUUM FULL implementation in cluster.c doesn't do any stats updating similar to vacuumlazy.c, so I haven't don't anything there… (is this right? A vacuum full may also encounter unremovable tuples, right?)
We've occasionally heard grumblings about making cluster do more stats
updating, but your patch should just go along with whatever's being
done now in similar cases.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-10-04 13:00:39 | Re: [v9.2] DROP statement reworks |
Previous Message | Robert Haas | 2011-10-04 12:22:04 | Re: Bug with pg_ctl -w/wait and config-only directories |