Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Horimoto Yasuhiro
    @komainu8
    What kind of case assume? Could you give me more details?
    Is the detail of this question explained in groonga/groonga#1132 ?
    Kartik Soneji
    @KartikSoneji
    Hi,
    I noticed an issue with the Mroonga compression library tests.
    Groonga does not compress text if the length is less than 256 bytes.
    In lib/store.c
    #define COMPRESS_THRESHOLD_BYTE 256
      if (value_len < COMPRESS_THRESHOLD_BYTE) {
        return grn_ja_put_packed(ctx, ja, id, value, value_len, flags, cas);
      }
    But the test string is only 62 bytes long, so it doesn't trigger compression.
    LZ4 , Zlib, ZStd
    INSERT INTO entries (id, content) VALUES (1, "I found Mroonga that is a MySQL storage engine to use Groonga!");
    Horimoto Yasuhiro
    @komainu8
    @KartikSoneji Thank you for your report! I'll add tests that they use a text the length is more than 256byte.
    Kartik Soneji
    @KartikSoneji
    @komainu8
    No problem.
    Should I open a pull request?
    Horimoto Yasuhiro
    @komainu8
    Thank you for your suggestion!
    Would you please send a pull request if possible?
    Kartik Soneji
    @KartikSoneji
    @komainu8 I have open a pull request: #350
    Please let me know if I need to change anything.
    Kartik Soneji
    @KartikSoneji
    Also, the Redmine site (http://redmine.groonga.org/projects/mroonga) seems to be broken:
    image.png
    Horimoto Yasuhiro
    @komainu8

    @komainu8 I have open a pull request: #350

    Thank you for your PR! I added a comment.

    Also, the Redmine site (http://redmine.groonga.org/projects/mroonga) seems to be broken:

    Thnak you for your report!
    We will disable this site.
    Because that is already not being used.

    Kartik Soneji
    @KartikSoneji

    Also, the Redmine site (http://redmine.groonga.org/projects/mroonga) seems to be broken:

    Thnak you for your report!
    We will disable this site.
    Because that is already not being used.

    Can you please update the documentation as well:
    https://mroonga.org/docs/developer.html#how-we-are-developing
    https://mroonga.org/docs/developer.html#roadmap
    https://mroonga.org/ja/docs/developer.html#how-we-are-developing
    https://mroonga.org/ja/docs/developer.html#roadmap

    @komainu8 I have open a pull request: #350

    Thank you for your PR! I added a comment.

    I will make the changes.

    I will make the changes.

    Thank you.

    Kartik Soneji
    @KartikSoneji
    @komainu8 I have made the changes, can you please check again: mroonga/mroonga#350
    Alex Vandiver
    @alexmv
    Heya! Would it be possible to add an IPv6 address, and AAAA record, for packages.groonga.org?
    Sutou Kouhei
    @kou
    Will do.
    Sutou Kouhei
    @kou
    Done.
    anthonydafc
    @anthonydafc

    hello can you explain why i get errors when doing un update of pgroonga when I type "ALTER EXTENSION pgroonga UPDATE;" error is : ERREUR: n'a pas pu charger la bibliothèque « C:/Program Files/PostgreSQL/9.6/lib/pgroonga.dll » : unknown error 126
    ** Erreur **

    ERREUR: n'a pas pu charger la bibliothèque « C:/Program Files/PostgreSQL/9.6/lib/pgroonga.dll » : unknown error 126
    État SQL :XX000

    Horimoto Yasuhiro
    @komainu8

    The cause of the error is that PostgreSQL doesn't find the library of PGroonga in a prescribed path (e.g.C:/Program Files/PostgreSQL/9.6/lib/pgroonga.dll).

    Could you show us the log of when PGroonga package updated?
    Then, could you teach us your PGroonga version before and after the upgrade?

    anthonydafc
    @anthonydafc
    Hello, i'm using postgres 9.6, i actually had pgroonga 2.0.1 and wanted to put new version 2.3.0, put had message after update. I've managed to update to 2.1.0 without error.
    Horimoto Yasuhiro
    @komainu8

    Ah... I'm sorry. I was mistaken about that your environment was Linux.

    Thanks.
    Please allow me to check that my understanding is correct or not about the following:

    • If you upgraded PGroonga to 2.1.0 from 2.0.1, you succeeded upgrade.
    • If you upgraded PGroonga to 2.3.0 from 2.0.1, you failed upgrade.

    I tried upggrade PGroonga to 2.3.0 from 2.0.1 on Windows10 Pro 20H2.
    This is successful.

    Could you confirm exist C:/Program Files/PostgreSQL/9.6/lib/pgroonga.dll?
    If this file whether it exists or not, could you install again with the following steps?

    1. Download PGroonga 2.3.0 from the following URL.

      (If your environment is 64bit.)
      https://github.com/pgroonga/pgroonga/releases/download/2.3.0/pgroonga-2.3.0-postgresql-9.6-x64.zip

      (If your environment is 32bit.)
      https://github.com/pgroonga/pgroonga/releases/download/2.3.0/pgroonga-2.3.0-postgresql-9.6-x86.zip

    2. Disconnect from all databases that use PGroonga.

    3. Expand the above zip file into the install folder of PostgreSQL 9.6(C:/Program Files/PostgreSQL/9.6/).
    4. Connect to a database that uses PGroonga.
    5. Upgrade PGroonga extension with the following SQL.

      ALTER EXTENSION pgroonga UPDATE;

    Zhanzhao (Deo) Liang
    @DeoLeung
    hi, is there a similar workflow example for pgroonga, I found this on groonga website "a database can receive read queries through the built-in HTTP server of Groonga while accepting update queries through MySQL."
    Sutou Kouhei
    @kou
    sudo -u postgres -H groonga --log-path /var/log/groonga/groonga.log --query-log-path /var/log/groonga/query.log --protocol http --pid-path /var/run/groogna.pid -d ${PG_DATA_DIR}/base/${DB_OID}/pgrn will work.
    Zhanzhao (Deo) Liang
    @DeoLeung
    I see. So is it possible if I use another table space(like a mounted nas) for pgrooga index, then I can start the groonga http service on another server, to scale out the read query? That depnds whether I can control the location of the pgrn folder
    Sutou Kouhei
    @kou
    You can't do it. Because ${PG_DATA_DIR}/base/${DB_OID}/pgrnfile isn't shared by a mounted NAS. The pgrn file has DB metadata. It's needed to open Groonga database.
    How about replicating your data by PostgreSQL's streaming replication feature to another servers?
    You can start a Groonga HTTP server on each replicated server.
    Zhanzhao (Deo) Liang
    @DeoLeung
    yes we are using replication at the moment, but our database it's quite large , we want to reduce the disk usage($$$). the second reason is we have several databases we want to support searching across them. if we can make pgrn kind of plugable that will be a great feature. (even for backup we can just copy the file :)
    Sutou Kouhei
    @kou
    You can sync Groonga DB by rsync -a --include '/pgrn*' --exclude '*' --delete ${PG_DATA_DIR}/base/${DB_OID}/ /mnt/nas/groonga/db/. (If you don't use tablespace.)
    You can use synced Groonga DB by another servers.
    Note that you must flush all changes in memory by select pgroonga_command('io_flush') before rsync and you must not update while rsync.
    If you update, rsync may sync broken DB.