Re: Remove 1MB size limit in tsvector

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Ildus K <i(dot)kurbangaliev(at)postgrespro(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove 1MB size limit in tsvector
Date: 2017-08-10 15:06:17
Message-ID: CAPpHfdvY-Rmt+keRc-ehPDwfu91FvSanwB7+ar1vnH-3KnWPTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 9, 2017 at 7:38 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Tue, Aug 1, 2017 at 4:00 PM, Ildus K <i(dot)kurbangaliev(at)postgrespro(dot)ru>
> wrote:
> > It's a workaround. DatumGetTSVector and
> > DatumGetTSVectorCopy will upgrade tsvector on the fly if it
> > has old format.
>
> Hmm, that seems like a real fix, not just a workaround. If you can
> transparently read the old format, there's no problem. Not sure about
> performance, though.
>

+1
Ildus, I think we need to benchmark reading of the old format. There would
be tradeoff between performance of old format reading and amount of extra
code needed. Once we will have benchmarks we can consider whether this is
the solution we would like to buy.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-08-10 15:11:06 Re: pl/perl extension fails on Windows
Previous Message Alexander Korotkov 2017-08-10 15:00:24 Re: Remove 1MB size limit in tsvector