| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ildus Kurbangaliev <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-01 18:56:54 |
| Message-ID: | CA+TgmoY2qxp7HBpDKQAsNDYn45cBRGOfjbmPmVx0=zfkx4GNjg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 1, 2017 at 10:08 AM, Ildus Kurbangaliev
<i(dot)kurbangaliev(at)postgrespro(dot)ru> wrote:
> Historically tsvector type can't hold more than 1MB data.
> I want to propose a patch that removes that limit.
>
> That limit is created by 'pos' field from WordEntry, which have only
> 20 bits for storage.
>
> In the proposed patch I removed this field and instead of it I keep
> offsets only at each Nth item in WordEntry's array.
So this would break pg_upgrade for tsvector columns?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2017-08-01 19:01:59 | JDBC 42.1.4 released |
| Previous Message | Fabien COELHO | 2017-08-01 18:49:29 | Re: pgbench minor doc typo |