| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Not HOT enough |
| Date: | 2011-11-23 15:20:44 |
| Message-ID: | 1322061559-sup-6871@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Robert Haas's message of mié nov 23 12:15:55 -0300 2011:
> > And it effects shared catalogs only, which are all low traffic anyway.
>
> I think "low traffic" is the key point. I understand that you're not
> changing the VACUUM behavior, but you are making heap_page_prune_opt()
> not do anything when a shared catalog is involved. That would be
> unacceptable if we expected shared catalogs to be updated frequently,
> either now or in the future, but I guess we don't expect that.
Maybe not pg_database or pg_tablespace and such, but I'm not so sure
about pg_shdepend. (Do we record pg_shdepend entries for temp tables?)
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-11-23 15:27:12 | Re: Permissions checks for range-type support functions |
| Previous Message | Robert Haas | 2011-11-23 15:15:55 | Re: Not HOT enough |