From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Ildus K <i(dot)kurbangaliev(at)postgrespro(dot)ru> |
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 16:38:35 |
Message-ID: | CA+TgmobcUow2Lw2Evqx=gVBhQLjTSWuUYGM1WnAf8UQ3DHKoew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-08-09 16:44:17 | Re: How can I find a specific collation in pg_collation when using ICU? |
Previous Message | Robert Haas | 2017-08-09 15:42:00 | Re: WIP: Failover Slots |