| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>, "List pgsql-patches" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Hint Bits and Write I/O |
| Date: | 2008-06-27 14:25:47 |
| Message-ID: | 87lk0rq7is.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Alvaro Herrera" <alvherre(at)commandprompt(dot)com> writes:
> If only VACUUM is going to set "flexible" to off, maybe it's better to
> leave the APIs as they are and have a global that's set by VACUUM only
> (and reset in a PG_CATCH block).
Ugh. Perhaps it would be simpler to have a wrapper function HTSV() macro which
passes flexible=true to HTSV_internal(). Then vacuum can call HTSV_internal().
I'm not sure what the performance tradeoff is between having an extra argument
to HTSV and having HTSV check a global which messes with optimizations.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-06-27 14:36:02 | Re: [HACKERS] Hint Bits and Write I/O |
| Previous Message | Richard Huxton | 2008-06-27 13:49:53 | ALTER DATABASE vs pg_dump |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-06-27 14:36:02 | Re: [HACKERS] Hint Bits and Write I/O |
| Previous Message | Bruce Momjian | 2008-06-27 12:32:30 | Re: Removal of the patches email list |