Re: tsvector_update_trigger() fails in 9.6 on character(2) column

From: Matt Magoffin <postgresql(dot)org(at)msqr(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: tsvector_update_trigger() fails in 9.6 on character(2) column
Date: 2017-03-09 07:32:19
Message-ID: 2C65FF85-4F9C-4432-89F8-1D1609C422C7@msqr.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


> On 9/03/2017, at 4:34 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Not entirely sure that it's worth the trouble, as this seems like a rather
> strange use-case to me.

Thanks for the info, Tom. I can speak to the use-case in my situation, where the char(2) column is but one of many columns added to a tsvector column via tsvector_update_trigger(), so that general user-entered search queries can execute (quickly) against the tsvector column alone.

Kind regards,
Matt

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Stepan Yankevych 2017-03-09 09:31:59 Re: BUG #14581: invalid cache ID: 41 CONTEXT: parallel worker
Previous Message Tom Lane 2017-03-09 03:34:46 Re: tsvector_update_trigger() fails in 9.6 on character(2) column