From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: An inconsistency in the documentation about full text search |
Date: | 2023-11-29 18:39:07 |
Message-ID: | 3e2a2d49-1241-4c48-90df-63f11d4bd45c@app.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, Nov 7, 2023, at 7:12 AM, Erki Eessaar wrote:
> Section
>
> 12.2.2. Creating Indexes
> https://www.postgresql.org/docs/current/textsearch-tables.html#TEXTSEARCH-TABLES-INDEX
>
> wrtites the following: "Another approach is to create a separate tsvector column to hold the output of to_tsvector. To keep this column automatically up to date with its source data, use a stored generated column. This example is a concatenation of title and body, using coalesce to ensure that one field will still be indexed when the other is NULL"
>
> Section
>
> 12.4.3. Triggers for Automatic Updates
> https://www.postgresql.org/docs/current/textsearch-features.html#TEXTSEARCH-UPDATE-TRIGGERS
This section has a note at the top that this trigger-based method is obsolete
and refers to section 12.2.2 (Creating Indexes).
--
Euler Taveira
EDB https://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2023-11-29 22:18:20 | Restore to a new database from a backup (.tar) generated from |
Previous Message | Eric Hanson | 2023-11-29 18:27:08 | Re: "name" vs "alias" in datatype table |