| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Clean up code associated with updating pg_class statistics |
| Date: | 2006-05-11 04:15:43 |
| Message-ID: | 20060511041543.GA2661@surnet.cl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
> Log Message:
> -----------
> Clean up code associated with updating pg_class statistics columns
> (relpages/reltuples). To do this, create formal support in heapam.c for
> "overwrite" tuple updates (including xlog replay capability) and use that
> instead of the ad-hoc overwrites we'd been using in VACUUM and CREATE INDEX.
> Take the responsibility for updating stats during CREATE INDEX out of the
> individual index AMs, and do it where it belongs, in catalog/index.c. Aside
> from being more modular, this avoids having to update the same tuple twice in
> some paths through CREATE INDEX. It's probably not measurably faster, but
> for sure it's a lot cleaner than before.
Minor comment: since you removed the ----- lines from the index_create
header comment, I think pgindent will mess up the alignment for that
comment, which probably will not be very nice. Same in
index_update_stats. Otherwise, nice work! I will update my relminxid
patch to this and re-submit.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Nwakefield | 2006-05-11 06:54:15 | bizgres - bizgres: Minor updates to logging components. |
| Previous Message | James William Pye | 2006-05-11 02:28:55 | python - rc: Reference the dbname option for, well, the dbname. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Bjorklund | 2006-05-11 04:41:35 | Re: BEGIN inside transaction should be an error |
| Previous Message | Jaime Casanova | 2006-05-11 02:43:32 | Re: BEGIN inside transaction should be an error |