Re: [HACKERS] Remove 1MB size limit in tsvector - Mailing list pgsql-hackers

From Ildus K
Subject Re: [HACKERS] Remove 1MB size limit in tsvector
Date
Msg-id 20170801230025.0449d477@postgrespro.ru
Whole thread Raw
In response to Re: [HACKERS] Remove 1MB size limit in tsvector  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] Remove 1MB size limit in tsvector
Re: [HACKERS] Remove 1MB size limit in tsvector
List pgsql-hackers
On Tue, 1 Aug 2017 15:33:08 -0400
Robert Haas <robertmhaas@gmail.com> wrote:

> On Tue, Aug 1, 2017 at 3:10 PM, Ildus K
> <i.kurbangaliev@postgrespro.ru> wrote:
> >> So this would break pg_upgrade for tsvector columns?  
> >
> > I added a function that will convert old tsvectors on the fly. It's
> > the approach used in hstore before.  
> 
> Does that mean the answer to the question that I asked is "yes, but I
> have a workaround" or does it mean that the answer is "no"?
> 

It's a workaround. DatumGetTSVector and
DatumGetTSVectorCopy will upgrade tsvector on the fly if it
has old format.

Regards,
Ildus Kurbangaliev



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Better way to handle suppression of CASCADE detailmessages
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] [PATCH v3] pg_progress() SQL function to monitorprogression of long running SQL queries/utilities