Check it out now and let me know what you searched on, and whether or not
you see an improvement over what it was ... Tom -and- Bruce suggested some
changes that, from my tests, show a dramatic change in speed *compared to
what it was* ... but that could just be that I'm getting lucky ...
On Thu, 1 Jan 2004, ezra epstein wrote:
> Yup,
>
> So slow in fact that I never use it. I did once or twice and gave up.
> It is ironic! I only come to the online docs when I already know the
> <where> part of my search and just go to that part or section. For
> everything else, there's google!
>
> SECURITY INVOKER site:postgresql.org
>
> Searched pages from postgresql.org for SECURITY INVOKER. Results 1 -
> 10 of about 141. Search took 0.23 seconds.
>
>
> Ahhh, that's better.
>
> Or use site:www.postgresql.org to avoid the archive listings, etc.
>
> == Ezra Epstein
>
> ""D. Dante Lorenso"" <dante@lorenso.com> wrote in message
> news:3FF0A316.7090300@lorenso.com...
> > Trying to use the 'search' in the docs section of PostgreSQL.org
> > is extremely SLOW. Considering this is a website for a database
> > and databases are supposed to be good for indexing content, I'd
> > expect a much faster performance.
> >
> > I submitted my search over two minutes ago. I just finished this
> > email to the list. The results have still not come back. I only
> > searched for:
> >
> > SECURITY INVOKER
> >
> > Perhaps this should be worked on?
> >
> > Dante
> >
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: the planner will ignore your desire to choose an index scan if your
> > joining column's datatypes do not match
> >
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
