> > As for searching spceific mailinglists, you can do that from the
> > archives search page already. Perhaps it needs to be made more
> > accessible or something?
>
> Amazing. What I like the most about it is that it actually works.
> Great!
that actually worked on the old one as well. The onl
I think it would be good to make it more prominent. Maybe have all the
search forms integrated on a single page and put a link to it in the top
menu, next to Support.
well, why not add a dropdown (or even better a multi-select input) on the
search page where users can choose what to search in:
On Tue, 19 Dec 2006, Thomas H. wrote:
http://search.postgresql.org/search?q=HAVING
says "An error occured while searching."
I bet HAVING is a stop-word, so actual message is 'NOTICE: query contains
only stopword(s) or doesn't contain lexeme(s), ignored'
I think we should add to pg_dict di
http://search.postgresql.org/search?q=HAVING
says "An error occured while searching."
I bet HAVING is a stop-word, so actual message is 'NOTICE: query contains
only stopword(s) or doesn't contain lexeme(s), ignored'
I think we should add to pg_dict dictionary line
having having
just a th
Magnus Hagander wrote:
> As for searching spceific mailinglists, you can do that from the
> archives search page already. Perhaps it needs to be made more
> accessible or something?
Amazing. What I like the most about it is that it actually works.
Great!
I think it would be good to make it more
On Dec 19, 2006, at 8:15 AM, Magnus Hagander wrote:
On Tue, Dec 19, 2006 at 01:02:09PM -0300, Alvaro Herrera wrote:
Matthew O'Connor wrote:
Magnus Hagander wrote:
But seriously, I'm definitly interested in ways it can be
improved - and
that's true of the whole web team, I'm sure. It was ju
On Tue, 19 Dec 2006, Filip Rembiakowski wrote:
2006/12/19, Joshua D. Drake <[EMAIL PROTECTED]>:
Take a look at let us know what you think and how it performs for you.
http://search.postgresql.org/search?q=HAVING
says "An error occured while searching."
I bet HAVING is a stop-word, so actua
2006/12/19, Joshua D. Drake <[EMAIL PROTECTED]>:
Take a look at let us know what you think and how it performs for you.
http://search.postgresql.org/search?q=HAVING
says "An error occured while searching."
F.
---(end of broadcast)---
TIP 5: do
On Tue, 2006-12-19 at 17:15 +0100, Magnus Hagander wrote:
> On Tue, Dec 19, 2006 at 09:41:38PM +0530, Gurjeet Singh wrote:
> > On 12/19/06, Matthew O'Connor wrote:
> > >
> > >Magnus Hagander wrote:
> > >> But seriously, I'm definitly interested in ways it can be improved - and
> > >> that's true o
On 12/19/06, Oleg Bartunov wrote:
On Tue, 19 Dec 2006, Gurjeet Singh wrote:
> On 12/19/06, Matthew O'Connor wrote:
>>
>> Magnus Hagander wrote:
>> > But seriously, I'm definitly interested in ways it can be improved -
and
>> > that's true of the whole web team, I'm sure. It was just my way of
Magnus Hagander wrote:
We still have a searchform at search.postgresql.org. To search
mainliglists, click Archives search. You can select a list, or a group
of list, there. Or just search them all.
Anyone see any value in allowing the mailing list search to be sorted by
both ascending and desc
On Tue, 19 Dec 2006, Gurjeet Singh wrote:
On 12/19/06, Matthew O'Connor wrote:
Magnus Hagander wrote:
> But seriously, I'm definitly interested in ways it can be improved - and
> that's true of the whole web team, I'm sure. It was just my way of
> saying "it will take a while", but I'll file
On Tue, Dec 19, 2006 at 01:02:09PM -0300, Alvaro Herrera wrote:
> Matthew O'Connor wrote:
> > Magnus Hagander wrote:
> > >But seriously, I'm definitly interested in ways it can be improved - and
> > >that's true of the whole web team, I'm sure. It was just my way of
> > >saying "it will take a whil
On Tue, 19 Dec 2006, Alvaro Herrera wrote:
Matthew O'Connor wrote:
Magnus Hagander wrote:
But seriously, I'm definitly interested in ways it can be improved - and
that's true of the whole web team, I'm sure. It was just my way of
saying "it will take a while", but I'll file it away as a good t
On Tue, Dec 19, 2006 at 09:41:38PM +0530, Gurjeet Singh wrote:
> On 12/19/06, Matthew O'Connor wrote:
> >
> >Magnus Hagander wrote:
> >> But seriously, I'm definitly interested in ways it can be improved - and
> >> that's true of the whole web team, I'm sure. It was just my way of
> >> saying "it
On 12/19/06, Matthew O'Connor wrote:
Magnus Hagander wrote:
> But seriously, I'm definitly interested in ways it can be improved - and
> that's true of the whole web team, I'm sure. It was just my way of
> saying "it will take a while", but I'll file it away as a good thing to
> do when there i
Matthew O'Connor wrote:
> Magnus Hagander wrote:
> >But seriously, I'm definitly interested in ways it can be improved - and
> >that's true of the whole web team, I'm sure. It was just my way of
> >saying "it will take a while", but I'll file it away as a good thing to
> >do when there is a moment
Magnus Hagander wrote:
But seriously, I'm definitly interested in ways it can be improved - and
that's true of the whole web team, I'm sure. It was just my way of
saying "it will take a while", but I'll file it away as a good thing to
do when there is a moment of spare time.
I like the way the
On Wed, Dec 20, 2006 at 01:35:57AM +1030, Shane Ambler wrote:
> Magnus Hagander wrote:
> >You get this if you go into say the 8.2 docs, and use the search form
> >there - same as before.
>
> I would search from the home page rather than navigate to docs first.
> (open browser - type postgres.org (
Magnus Hagander wrote:
On Tue, Dec 19, 2006 at 12:56:25AM +0100, Thomas H. wrote:
Take a look at let us know what you think and how it performs for you.
i would love an advanced search where you can limit the results to a
particular version of the documentation. the query for "SELECT" returns t
Hi,
Seems ok. Works better than most corporate search engines - some tend
to show pages and pages of useless press releases when you are
searching for drivers, specifications etc.
But as long as the sites remain indexable to outside search engines,
people get to use whichever search engine t
On Tue, Dec 19, 2006 at 01:24:01PM +0100, Magnus Hagander wrote:
> On Tue, Dec 19, 2006 at 01:13:16PM +0300, Oleg Bartunov wrote:
> > >Seems to_tsvecto() returns NULL for tsearch2 or for, as you say,
> > >anything that ends in a digit.
> > >
> > >Oleg, can you comment on why this is happening? What
On Tue, Dec 19, 2006 at 01:13:16PM +0300, Oleg Bartunov wrote:
> >Seems to_tsvecto() returns NULL for tsearch2 or for, as you say,
> >anything that ends in a digit.
> >
> >Oleg, can you comment on why this is happening? What can we do to fix
> >that?
>
> Most probably, token type 'word' just doesn
On Tue, 19 Dec 2006, Magnus Hagander wrote:
On Tue, Dec 19, 2006 at 01:48:22PM +0530, Gurjeet Singh wrote:
On 12/19/06, Henrik Zagerholm <[EMAIL PROTECTED]> wrote:
Hello,
Searching after "tsearch"
5. PostgreSQL: Documentation: Manuals: PostgreSQL 7.4: Examples [0.1]
...tsearch and tsearch2Fu
On Tue, Dec 19, 2006 at 01:48:22PM +0530, Gurjeet Singh wrote:
> On 12/19/06, Henrik Zagerholm <[EMAIL PROTECTED]> wrote:
> >
> >Hello,
> >
> >Searching after "tsearch"
> >5. PostgreSQL: Documentation: Manuals: PostgreSQL 7.4: Examples [0.1]
> >...tsearch and tsearch2Full text
> >indexingPrevHomeNe
On Tue, Dec 19, 2006 at 12:56:25AM +0100, Thomas H. wrote:
> >Take a look at let us know what you think and how it performs for you.
>
> i would love an advanced search where you can limit the results to a
> particular version of the documentation. the query for "SELECT" returns too
> many resul
On 12/19/06, Shane Ambler <[EMAIL PROTECTED]> wrote:
> I echo Thomas' request to have docs limited to a version (or, better,
> most recent). Perhaps archived docs should be searched via a separate
> page entirely.
+1 there - current docs should be searched unless you specify all/older
count
On 12/19/06, Henrik Zagerholm <[EMAIL PROTECTED]> wrote:
Hello,
Searching after "tsearch"
5. PostgreSQL: Documentation: Manuals: PostgreSQL 7.4: Examples [0.1]
...tsearch and tsearch2Full text
indexingPrevHomeNextLimitationsUpPage Files User Comments No comments
could be found for this...
http:
Reece Hart wrote:
On Mon, 2006-12-18 at 15:47 -0800, Joshua D. Drake wrote:
Take a look at let us know what you think and how it performs for you.
Terrific. Fast and meaningful.
I echo Thomas' request to have docs limited to a version (or, better,
most recent). Perhaps archived docs should
Hello,
Searching after "tsearch"
5. PostgreSQL: Documentation: Manuals: PostgreSQL 7.4: Examples [0.1]
...tsearch and tsearch2Full text
indexingPrevHomeNextLimitationsUpPage Files User Comments No comments
could be found for this...
http://www.postgresql.org/docs/7.4/interactive/examples.htm
On Mon, 2006-12-18 at 15:47 -0800, Joshua D. Drake wrote:
> Take a look at let us know what you think and how it performs for you.
Terrific. Fast and meaningful.
I echo Thomas' request to have docs limited to a version (or, better,
most recent). Perhaps archived docs should be searched via a se
"Thomas H." <[EMAIL PROTECTED]> writes:
> i would love an advanced search where you can limit the results to a
> particular version of the documentation. the query for "SELECT" returns too
> many results from too many versions, obviously.
+1 on that.
> its fast & quick tho :-)
Indeed.
Be seei
Take a look at let us know what you think and how it performs for you.
i would love an advanced search where you can limit the results to a
particular version of the documentation. the query for "SELECT" returns too
many results from too many versions, obviously.
its fast & quick tho :-)
re
Hello,
search.postgresql.org is now served directly from PostgreSQL 8.2 ,
Tsearch2 and GIN. We have been testing thoroughly for the last couple of
weeks but of course... it is now open to the general public.
Take a look at let us know what you think and how it performs for you.
Sincerely,
Joshu
34 matches
Mail list logo
