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

From Torsten Zuehlsdorff
Subject Re: [HACKERS] Remove 1MB size limit in tsvector
Date
Msg-id 8fd83aca-5e0c-054e-29df-787407f9bcf9@toco-domains.de
Whole thread Raw
In response to Re: [HACKERS] Remove 1MB size limit in tsvector  (Ildus K <i.kurbangaliev@postgrespro.ru>)
Responses Re: [HACKERS] Remove 1MB size limit in tsvector  (Ildus Kurbangaliev <i.kurbangaliev@postgrespro.ru>)
List pgsql-hackers

On 01.08.2017 22:00, Ildus K wrote:
> 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.

I'm not familiar with pg_upgrade, but want to ask: should this 
workaround be part of pg_upgrade?

Greetings,
Torsten



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Timing-sensitive case in src/test/recovery TAP tests
Next
From: Rajkumar Raghuwanshi
Date:
Subject: Re: [HACKERS] Default Partition for Range