Re: An inconsistency in the documentation about full text search - Mailing list pgsql-docs

From Euler Taveira
Subject Re: An inconsistency in the documentation about full text search
Date
Msg-id 3e2a2d49-1241-4c48-90df-63f11d4bd45c@app.fastmail.com
Whole thread Raw
In response to An inconsistency in the documentation about full text search  (Erki Eessaar <erki.eessaar@taltech.ee>)
List 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

pgsql-docs by date:

Previous
From: Eric Hanson
Date:
Subject: Re: "name" vs "alias" in datatype table
Next
From: PG Doc comments form
Date:
Subject: Restore to a new database from a backup (.tar) generated from