Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

英語ページを用意する #3

Closed
5 tasks done
kou opened this issue Mar 29, 2015 · 3 comments
Closed
5 tasks done

英語ページを用意する #3

kou opened this issue Mar 29, 2015 · 3 comments

Comments

@kou
Copy link
Member

kou commented Mar 29, 2015

@uhyoppo
Copy link

uhyoppo commented Sep 3, 2015

翻訳しかけたんですが、似たような英文が既にあったので、もう要らないのかと思ってました。校正してないですけど、せっかくなんで貼っときますね。

PGroonga (píːzí:lúnɡά)

Release Information

Refer to news.md

Overview

PGroonga is a PostgreSQL extension to use Groonga as the index.

As default, PostgreSQL is not capable for full-text-searching for Japanese text data. PGroonga can do with remarkable speed. Similar extensions are known for the full-text searching as below:

  • pg_trgm
    • Bundled with PostgreSQL but not installed as default
    • Source code modification is required to adapt for Japanese
  • pg_bigm
    • Source code modification is NOT required to adapt for Japanese
    • But for the exact result:
      Enabling Recheck function is mandantory.
    • If recheck is enabled, PostgreSQL will search using index, then search again sequentially against the result of the first search; therefore the cost tends to be increased if there are many results at the first searching.
    • If recheck is disabled, there are possibilities to match the records which doesn't include the keyword.

The modification of the original PostgreSQL source code is NOT required for PGroonga like pg_trgm.

PGroonga can return the exact result without recheck like pg_bigm. Therefore, the result using index which has many records, doesn't prevent the speed as pg_bigm does. (Theoretically, the verification should be done using benchmark test. We need volunteers.)

However, at this stage, PGroonga doesn't mention to WAL, so it can't adapt to the crash recovery function and the replication. (pg_trgm and pg_bigm can act with them because GIN and GiST can do it, which are used in pg_trgm and pg_bigm.)

(*) Currently PostgreSQL doesn't provide API for the index as the extension functionalities to adapt to WAL. If such API would be provided, we will follow it immediately.

PostgreSQL versions which can install Pgroonga

  • PostgreSQL 9.3
  • PostgreSQL 9.4

Installation

We made the packages for the environments below:

  • Debian GNU/Linux Jessie
  • Ubuntu 14.04
  • Ubuntu 14.10
  • Ubuntu 15.04
  • CentOS 5
  • CentOS 6
  • CentOS 7
  • Windows 32bit + PostgreSQL 9.4.2
  • Windows 64bit + PostgreSQL 9.4.2

You must use the source code to install on the other environments.

Details of installation for each environment will continue at the next sections below.

kou added a commit that referenced this issue Sep 4, 2015
GitHub: #3

Based on translation by Uhyoppo the Great. Thanks!!!
@kou
Copy link
Member Author

kou commented Sep 4, 2015

ありがとうございます!
発音記号なんかは私は絶対書けないやつなのでとても助かります!

今の翻訳に反映しました!

@kou
Copy link
Member Author

kou commented Oct 29, 2015

Done!

@kou kou closed this as completed Oct 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants