From: | Alexander Hill <alex(at)hill(dot)net(dot)au> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #8354: stripped positions can generate nonzero rank in ts_rank_cd |
Date: | 2014-03-21 06:29:26 |
Message-ID: | CA+KBOKxzfHNT96i_Ct6304OEmHUAzY+-sa-OdK7XgSSb-bx3eA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi Bruce,
I've just updated the docs for ts_rank_cd in my fork to reflect this
change. Would be great if that could make it in too.
Patch here:
https://github.com/AlexHill/postgres/commit/3e5d86ea23d82b07188192411cdc5c5a5194a5ae.patch
Is there anything else I need to do to make sure this patch ends up in 9.4?
Cheers,
Alex
On Feb 12, 2014 10:31 PM, "Bruce Momjian" <bruce(at)momjian(dot)us> wrote:
> On Wed, Feb 12, 2014 at 09:49:32AM +0800, Alexander Hill wrote:
> > Hi Bruce,
> >
> > In normal use this won't affect any data that ends up in an index.
> >
> > The only exception would be where somebody has created an index over the
> result
> > of ts_rank_cd - indexing search rank for the most common search terms,
> maybe?
>
> OK, good.
>
> > But that's true of any function whose result is indexed. What's the
> upgrade
> > policy in that case?
>
> Well, we document that the function output changed, and if anyone is
> using the function for an index, they need to rebuild the index, so I
> think we are fine fixing this for 9.4.
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + Everyone has their own god. +
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2014-03-21 13:43:23 | Re: BUG #8354: stripped positions can generate nonzero rank in ts_rank_cd |
Previous Message | darius | 2014-03-21 06:17:35 | BUG #9652: inet types don't support min/max |