Hi,
Am 15.11.2006 um 15:34 schrieb Gurjeet Singh:
=
.) The SELECTs in the pg_advise are returning wrong results, when
the same index is suggested twice, because of the SUM() aggregates.
I don't think that this is a bug. If the same index is recommended
for two different queries it will ap
Hi Gurjeet,
I will look at the pg_advise bug and will send a patch ASAP.
Best,
Kai
Am 15.11.2006 um 15:34 schrieb Gurjeet Singh:
BUGS:
=
.) The SELECTs in the pg_advise are returning wrong results, when
the same index is suggested twice, because of the SUM() aggregates.
.) I doubt that o
Hi Gurjeet,
I include pgsql-hackers in this discussion ...
Am 01.11.2006 um 17:38 schrieb Gurjeet Singh:
Hi Kai,
I am working with Simon at EnterpriseDB, and am currently
working on porting
your patch to 8.2 sources. I have done a quick hack to make it work
on 8.2;
please find the modi
Hi,
Am 11.10.2006 um 19:39 schrieb Simon Riggs:
I'm sure everybody would be glad to see the existing work submitted
as a
Work-in-Progress patch to pgsql-patches.
Would a patch against a clean 7.4.8 source tree useful for you?
Otherwise, I had to spend some time to migrate the code to 8.2..
Hi,
sorry for opening a new thread but I have just subscribed to the
list. We have already an implementation of an index advisor for
7.4.8. This is the result of several master theses, so it's no
production ready yet, but it works (with some limitations).
The main idea is:
1. to run the pl
