| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fix for Index Advisor related hooks |
| Date: | 2011-02-17 00:53:19 |
| Message-ID: | AANLkTi=DqPXZEWWxFYvOPzvEJNnGgUES_cLzoTGioBPR@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17 February 2011 00:48, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thom Brown <thom(at)linux(dot)com> writes:
>> For my benefit, could you explain how ishypothetical gets set to true?
>
> In the core, it never does. An index advisor plugin would set it in
> IndexOptInfo structs that it makes.
I get the idea. Thanks Tom.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-02-17 00:53:28 | pgsql: Fix blatantly uninitialized variable in recent commit. |
| Previous Message | Tom Lane | 2011-02-17 00:48:55 | Re: Fix for Index Advisor related hooks |