| From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PERFORM] encouraging index-only scans |
| Date: | 2013-09-06 11:38:56 |
| Message-ID: | 5229BED0.5070506@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On 09/06/2013 09:23 AM, Dimitri Fontaine wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> I'm not sure if we need to expose all these new maintenance actions as
>> SQL commands.
> I strongly think we should, if only for diagnostic purposes.
It would be much easier and more flexible to expose them
as pg_*() function calls, not proper "commands".
> Also to
> adapt to some well defined workloads that the automatic system is not
> designed to handle.
+1
--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Agustin Larreinegabe | 2013-09-06 12:12:05 | |
| Previous Message | Greg Stark | 2013-09-06 10:30:10 | Re: Analysis on backend-private memory usage (and a patch) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-09-06 13:08:54 | Re: [PERFORM] encouraging index-only scans |
| Previous Message | Ľubomír Varga | 2013-09-06 08:44:20 | Re: planner and having clausule |