| From: | Ildus K <i(dot)kurbangaliev(at)postgrespro(dot)ru> |
|---|---|
| To: | 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-01 20:00:25 |
| Message-ID: | 20170801230025.0449d477@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Regards,
Ildus Kurbangaliev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-08-01 20:06:43 | Re: [PATCH v3] pg_progress() SQL function to monitor progression of long running SQL queries/utilities |
| Previous Message | Alvaro Herrera | 2017-08-01 19:59:30 | Re: Better way to handle suppression of CASCADE detail messages |