ional feature.
Best,
Kai
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
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
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
o 8.2...
Best,
Kai
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
ottlenecks (creating virtual
indexes, calling the planner twice) but I think they can be solved.
So, let me know if you are interested,
Kai
---(end of broadcast)---
TIP 6: explain analyze is your friend
s that the selects above should be among the default set of
operations on inet values in PostgreSQL, being subtraction and addition. If
not I'd like to be proven wrong.
Regards,
Kai
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
