Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sRWMp-00G5Ve-7R for pgsql-announce@arkaria.postgresql.org; Wed, 10 Jul 2024 12:24:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sRWMn-004NqM-Pp for pgsql-announce@arkaria.postgresql.org; Wed, 10 Jul 2024 12:24:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sRWMm-004NpB-MS for pgsql-announce@lists.postgresql.org; Wed, 10 Jul 2024 12:24:12 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sRWMg-001Mlw-AD for pgsql-announce@lists.postgresql.org; Wed, 10 Jul 2024 12:24:11 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=8Fw+Tu+/xyQ5R0R/bIzXb2FY/AHd5GwRdXbXHgQsJ2k=; b=lQLX5WbB9NiXqq7PVejnu1iPn0 JXUWYMj5ajkVQN5c9lQ68zSv5ENzdw7c+58sY5twyhy/k8282rcOOy0lofZEcs+JDW3tVM0q+f3AR 3xTUl25wZHIkwN0G/NEgzy61031e5TfBrAoEr0JbzuPlEv9jrBy8SfjmtL9RTgJl+SEFCHxPO2Nzq 5AeOU66CDot5chtJvIkKNbjCNQeLpQ/76VjxJ+Ek5zmhzXIoCuUxfqTNxHQhXyPX3LDgl0xCdDts1 kmRmPmpEN+V3dfy3RAdgSEzb/GfBZWVAJHFzU9RUoSSOm3YpKp27GO88vjjHxVQ1DLuWWHQ0f7XPU 4UevkZMA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sRWMf-004BxS-0H for pgsql-announce@lists.postgresql.org; Wed, 10 Jul 2024 12:24:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sRWMd-006yih-Gp for pgsql-announce@lists.postgresql.org; Wed, 10 Jul 2024 12:24:03 +0000 Content-Type: multipart/mixed; boundary="===============6988142234506885897==" MIME-Version: 1.0 Subject: PGroonga 3.2.1 - Multilingual fast full text search To: PostgreSQL Announce From: PGroonga project via PostgreSQL Announce Reply-To: kou@clear-code.com Date: Wed, 10 Jul 2024 12:23:38 +0000 Message-ID: <172061421821.736592.6916114347262795288@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 8bef680f4eaddc45cf1801eed0944c9d315657fed188be5665b3b032f4bcd192 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============6988142234506885897== Content-Type: multipart/alternative; boundary="===============7406942875547927990==" MIME-Version: 1.0 --===============7406942875547927990== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi, PGroonga 3.2.1 has been released! This release adds support for WAL resource manager! With the WAL resource manager support, you can solve the following problems with the general WAL approach in PGroonga < 3.2.1: * You need to remove old WAL manually to avoid unlimited storage usage * You need to use additional mechanism to apply WAL in background * You need to recover from a crash after PostgreSQL started See also the following document how to use this feature: [Streaming replication by WAL resource manager](https://pgroonga.github.io/= reference/streaming-replication-wal-resource-manager.html) Note that you need PostgreSQL 15 or later because this is based on custom WAL resource manager feature that is available since PostgreSQL 15. = If you're interesting in how to implement the WAL resource manager, see also the following blog post: Japanese: [How to implement the PGroonga's WAL resource manager](https://www.clear-co= de.com/blog/2024/7/5/pgroonga-custom-wal-resource-manager.html) English: [Google Translate of the post](https://www-clear--code-com.translate.goog/b= log/2024/7/5/pgroonga-custom-wal-resource-manager.html?_x_tr_sl=3Dja&_x_tr_= tl=3Den&_x_tr_hl=3Dja&_x_tr_pto=3Dwapp) ### About PGroonga [PGroonga](https://pgroonga.github.io/) is a PostgreSQL extension that makes PostgreSQL fast full text search platform for all languages! It's released under PostgreSQL license. There are some PostgreSQL extensions that improves full text search feature of PostgreSQL such as pg_trgm[^1]. [^1]:https://www.postgresql.org/docs/current/static/pgtrgm.html pg_trgm doesn't support languages that use non-alphanumerics characters such as Japanese and Chinese. PGroonga supports all languages, provides rich full text search related features and is very fast. Because PGroonga uses Groonga[^2] that is a full-fledged full text search engine as backend. [^2]: https://groonga.org/ See the following benchmark results for performance: * Benchmark result for PGroonga, textsearch and pg_trgm with English Wiki= pedia https://pgroonga.github.io/reference/pgroonga-versus-textsearch-and-pg-= trgm.html * Benchmark result for PGroonga and pg_bigm with Japanese Wikipedia https://pgroonga.github.io/reference/pgroonga-versus-pg-bigm.html PGroonga also supports JSON search. You can use each value for condition. You can also perform full text search against all texts in JSON like textsearch in PostgreSQL. ### Changes Here are highlights in PGroonga 3.2.1: * Added support for WAL resource manager * Added support for downgrading by using `ALTER EXTENSION ... UPDATE` * Added support for Ubuntu 24.04 (Noble Numbat) * Added support for typo-tolerance search * Fixed some crash bugs See also [the 3.2.1 release note](https://pgroonga.github.io/news/#version-= 3-2-1) for full changes. ### Usage You can use PGroonga without full text search knowledge. You just create an index and puts a condition into WHERE: CREATE INDEX index_name ON table USING pgroonga (column); SELECT * FROM table WHERE column &@~ 'PostgreSQL'; You can also use LIKE to use PGroonga. PGroonga provides a feature that performs LIKE with index. LIKE with PGroonga index is faster than LIKE without index. It means that you can improve performance without changing your application that uses the following SQL: SELECT * FROM table WHERE column LIKE '%PostgreSQL%'; Are you interested in PGroonga? Please install[^4] and try tutorial[^5]. You can know all PGroonga features. [^4]: https://pgroonga.github.io/install/ [^5]: https://pgroonga.github.io/tutorial/ You can install PGroonga easily. Because PGroonga provides packages for major platforms. There are binaries for Windows. Thanks, --===============7406942875547927990== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PGroonga 3.2.1 - Multilingual fast full text search
 

PGroonga 3.2.1 - Multilingual fast full text search

Hi,

PGroonga 3.2.1 has been released!

This release adds support for WAL resource = manager!

With the WAL resource manager support, you = can solve the following problems with the general WAL approach in PGroonga < 3.2.1:

  • You need to rem= ove old WAL manually to avoid unlimited storage usage
  • You need to use= additional mechanism to apply WAL in background
  • You need to rec= over from a crash after PostgreSQL started

See also the following document how to use = this feature: = Streaming replication by WAL resource manager

Note that you need PostgreSQL 15 or later b= ecause this is based on custom WAL resource manager feature that is available since PostgreSQL 15. =

If you're interesting in how to implement t= he WAL resource manager, see also the following blog post:

Japanese: Ho= w to implement the PGroonga's WAL resource manager

English: Google Translate of the post

About PGroonga

PGroonga is a Postgre= SQL extension that makes PostgreSQL fast full text search platform for all languages! It's released under PostgreSQL license.

There are some PostgreSQL extensions that i= mproves full text search feature of PostgreSQL such as pg_trgm^1.

pg_trgm doesn't support languages that use = non-alphanumerics characters such as Japanese and Chinese.

PGroonga supports all languages, provides r= ich full text search related features and is very fast. Because PGroonga uses Groonga^2 t= hat is a full-fledged full text search engine as backend.

See the following benchmark results for per= formance:

  • Benchmark resul= t for PGroonga, textsearch and pg_trgm with English Wikipedia https://pgroonga.github.io/reference/pgroonga-versus-textsearch-and-pg-= trgm.html
  • Benchmark resul= t for PGroonga and pg_bigm with Japanese Wikipedia https://pgroonga.github.io/reference/pgroonga-versus-pg-bigm.html

PGroonga also supports JSON search. You can= use each value for condition. You can also perform full text search against all texts in JSON like textsearch in PostgreSQL.

Changes

Here are highlights in PGroonga 3.2.1:

  • Added support f= or WAL resource manager
  • Added support f= or downgrading by using ALTER EXTENSION ... UPDATE
  • Added support f= or Ubuntu 24.04 (Noble Numbat)
  • Added support f= or typo-tolerance search
  • Fixed some cras= h bugs

See also the 3.2.1 release note for full changes.

Usage

You can use PGroonga without full text sear= ch knowledge. You just create an index and puts a condition into WHERE:

CREATE INDEX index_name ON table USING pgroonga (column);
SELECT * FROM table WHERE column &@~ 'PostgreSQL';

You can also use LIKE to use PGroonga. PGro= onga provides a feature that performs LIKE with index. LIKE with PGroonga index is faster than LIKE without index. It means that you can improve performance without changing your application that uses the following SQL:

SELECT * FROM table WHERE column LIKE '%PostgreSQL%';

Are you interested in PGroonga? Please inst= all^4 and try tutorial^5. You can know all PGroonga featur= es.

You can install PGroonga easily. Because PG= roonga provides packages for major platforms. There are binaries for Windows.

Thanks,
This email was sent to you from PGroonga project. It was delivered on their= behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to PGroonga project.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============7406942875547927990==-- --===============6988142234506885897==--