From: | Torsten Zuehlsdorff <mailinglists(at)toco-domains(dot)de> |
---|---|
To: | Ildus K <i(dot)kurbangaliev(at)postgrespro(dot)ru>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Remove 1MB size limit in tsvector |
Date: | 2017-08-09 07:01:44 |
Message-ID: | 8fd83aca-5e0c-054e-29df-787407f9bcf9@toco-domains.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 01.08.2017 22:00, Ildus K wrote:
> On Tue, 1 Aug 2017 15:33:08 -0400
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>> On Tue, Aug 1, 2017 at 3:10 PM, Ildus K
>> <i(dot)kurbangaliev(at)postgrespro(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Rajkumar Raghuwanshi | 2017-08-09 07:07:43 | Re: Default Partition for Range |
Previous Message | Michael Paquier | 2017-08-09 06:45:37 | Re: Timing-sensitive case in src/test/recovery TAP tests |