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

From Robert Haas
Subject Re: [HACKERS] Remove 1MB size limit in tsvector
Date
Msg-id CA+TgmobcUow2Lw2Evqx=gVBhQLjTSWuUYGM1WnAf8UQ3DHKoew@mail.gmail.com
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  (Michael Paquier <michael.paquier@gmail.com>)
Re: [HACKERS] Remove 1MB size limit in tsvector  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
List pgsql-hackers
On Tue, Aug 1, 2017 at 4:00 PM, Ildus K <i.kurbangaliev@postgrespro.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.

The patch doesn't really conform to our coding standards, though, so
you need to clean it up (or, if you're not sure what you need to do,
you need to have someone who knows how PostgreSQL code needs to look
review it for you).

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] WIP: Failover Slots
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] How can I find a specific collation in pg_collationwhen using ICU?