Navigation Menu

Skip to content

Releases: pgroonga/pgroonga

PGroonga 3.2.0: 2024-04-18

18 Apr 09:20
Compare
Choose a tag to compare

Fixes

  • Fixed a crash on connection close.

    This occurred when the connection was closed "during a transaction
    and when releasing resources for a sequential search".

    This was caused by a callback being run to release a sequential search
    resource even though all resources had already been released.

    Fixed unregistration of callbacks that are no longer needed when releasing
    all resources.

PGroonga 3.1.9: 2024-03-27

27 Mar 03:29
Compare
Choose a tag to compare

Improvements

  • Added pgroonga_crash_safer.max_recovery_threads parameter to pgroonga-crash-safer.

PGroonga 3.1.8: 2024-02-27

27 Feb 07:53
Compare
Choose a tag to compare

Fixes

  • Fixed a crash bug when the last cached sequential search datum was vacuumed that is happen every 100 queries.

    Note that "vacuum" here is PGroonga internal vacuum only for sequential search datum.
    It's not PostgreSQL's vacuum.

    For example, we are crashed PGroonga by executing in the following procedure.

    1. We send the following query to PostgreSQL.

      SELECT WHERE content &@ ('hello', null, 'memos_index')::pgroonga_full_text_search_condition;.

    2. We send hundred non PGroonga's sequential search related queries such as SELECT 1;.

    3. We send the query same as 1. to PostgreSQL again.

PGroonga 3.1.7: 2024-02-05

05 Feb 07:59
Compare
Choose a tag to compare

Improvements

  • PGroonga avoid blocking of process termination while pgroonga-crash-safer is flushing.

Fixes

  • [pgroonga_highlight_html function] Fixed a bug that PGroonga may crash if valid index name is specified and then an invalid index name is specified.

PGroonga 3.1.6: 2024-01-10

10 Jan 05:20
Compare
Choose a tag to compare

Improvements

  • Added a new script for setting up the build environment. [GitHub#358][Patched by askdkc]

  • Added a new option pgroonga.enable_row_level_security.

    If we disabled pgroonga.enable_row_level_security, PGroonga might improve performance.
    However, it has a security risk.

    So, we must not disable this option when we use RLS.
    We must check whether we don't use RLS before we disable this.

  • Added new type pgroonga_condition and new function pgroonga_condition().

    pgroonga_full_text_search_condition type and pgroonga_full_text_search_condition_with_scorers type are deprecated.
    We use pgroonga_condition type instead.

    Here is the signature of pgroonga_condition().

    pgroonga_condition(query text,
                       weights int[],
                       scorers text[],
                       schema_name text,
                       index_name text,
                       column_name text)
    

Fixes

  • Fixed a bug if we update PGroonga from 2.4.1 to 2.4.2, we can't use pgroonga_snippet_html(). [Reported by takadat]

  • Fixed a bug if we specify non PostgreSQL's table as the first argument of pgroonga_query_expand(), PGroonga crashes as below.

    CREATE EXTENSION IF NOT EXISTS postgres_fdw;
    
    CREATE SERVER remote_server
        FOREIGN DATA WRAPPER postgres_fdw
        OPTIONS (host 'localhost', port '5432', dbname 'remote_database');
    
    CREATE FOREIGN TABLE synonym_groups (
      synonyms text[]
    ) SERVER remote_server;
    
    SELECT pgroonga_query_expand('synonym_groups',
                                 'synonyms',
                                 'synonyms',
                                 'groonga');
    
    server closed the connection unexpectedly
    	This probably means the server terminated abnormally
    	before or while processing the request.
    The connection to the server was lost. Attempting reset: Failed.
  • Fixed a bug if many error occured in PGroonga, PostgreSQL might consume all error stack and PANIC.

    This problem might occure since PGroonga 2.3.3.

Thanks

  • askdkc
  • takadat

PGroonga 3.1.5: 2023-09-29

29 Sep 05:36
Compare
Choose a tag to compare

Fixes

  • [pgroonga_highlight_html function] [[&@~
    operator][query-v2] and so on for sequential search] Fixed a crash
    bug when nonexistent attribute name in the index is specified.

PGroonga 3.1.4: 2023-09-29

28 Sep 13:08
Compare
Choose a tag to compare
  • [dump-wal] Added support for start from the specific position.

  • Renamed master branch to main branch.

  • Added support for PostgreSQL 16.

  • Dropped support for Amazon Linux 2.

  • Added tokenizer_mapping option that can be used to customize tokenizer for each indexed target.

  • [&` operator] Raised an error for sequential scan explicitly.

  • [pgroonga_highlight_html function],[sequential search] Added support for specifying full index name.

PGroonga 3.1.3: 2023-08-17

17 Aug 09:04
Compare
Choose a tag to compare

Fixes

  • pgroonga_highlight_html function: Fixed a
    crash bug. This may be occurred only when you use
    NormalizerTable in your index and specify the index that uses
    NormalizerTable.

  • Fixed a bug that PGroonga WAL may not be applied on standbys.

    This isn't caused by broken PGroonga WAL. So you can fix this
    problem by just upgrading your PGroonga to 3.1.3 or later.

PGroonga 3.1.2: 2023-08-09

09 Aug 12:06
Compare
Choose a tag to compare

Improvements

  • [Crash safe] Added support for resetting WAL applied
    position automatically on startup only on primary.

    Note that this is not done on standbys because WAL applied
    position may not be the latest on standbys.

  • [pgroonga_standby_maintainer.max_parallel_wal_appliers_per_db parameter]
    Added support for parallel WAL application.

Fixes

  • Fixed a crash bug in sequential search. This may be occurred only
    when you use NormalizerTable in your index and specify the index
    that uses NormalizerTable by
    pgroonga_full_text_search_condition or
    pgroonga_full_text_search_condition_with_scorers.

PGroonga 3.1.1: 2023-07-25

26 Jul 05:17
Compare
Choose a tag to compare

Improvements

  • [Debian] Added support for Debian GNU/Linux bookworm.