Navigation Menu

Skip to content

Commit

Permalink
Start translating overview
Browse files Browse the repository at this point in the history
  • Loading branch information
kou committed Oct 12, 2015
1 parent 08fa540 commit 55b5850
Show file tree
Hide file tree
Showing 2 changed files with 148 additions and 0 deletions.
104 changes: 104 additions & 0 deletions _po/ja/overview/index.po
@@ -0,0 +1,104 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"PO-Revision-Date: 2015-10-12 23:17+0900\n"
"Language: ja\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"

msgid ""
"---\n"
"title: Overview\n"
"layout: en\n"
"---"
msgstr ""
"---\n"
"title: 概要\n"
"layout: ja\n"
"---"

msgid "# Overview"
msgstr "# 概要"

msgid ""
"PGroonga is a PostgreSQL extension. PGroonga provides a new index that uses [G"
"roonga](http://groonga.org/)."
msgstr ""

msgid ""
"Groonga is an embeddable super fast full text search engine. It can be embedde"
"d into MySQL. [Mroonga](http://mroonga.org/) is a storage engine that is based"
" on Groonga. Groonga can also work as standalone search engine."
msgstr ""

msgid ""
"As default, PostgreSQL isn't capable for CJK full text search. But you can use"
" super fast CJK full text search by installing PGroonga."
msgstr ""

msgid ""
"And more, PGroonga supports full text search against all text values in JSON. "
"It's an unique feature. Built-in PostgreSQL features and [JsQuery](https://git"
"hub.com/postgrespro/jsquery) don't support it."
msgstr ""

msgid "## Related extensions"
msgstr ""

msgid "There are some extensions that implements CJK ready full text search:"
msgstr ""

msgid ""
" * [pg_trgm](http://www.postgresql.org/docs/9.4/static/pgtrgm.html)\n"
" * It's bundled with PostgreSQL but it's not installed as default.\n"
" * You need to change pg\\_trgm source code to support CJK."
msgstr ""

msgid ""
" * [pg_bigm](http://pgbigm.osdn.jp/)\n"
" * It supports CJK without changing source code.\n"
" * It requires [Recheck](http://pgbigm.osdn.jp/pg_bigm_en-1-1.html#enable_r"
"echeck) to remove false positives.\n"
" * Recheck is slow for many hits case. Because Recheck does sequential sear"
"ch against records found by index search.\n"
" * If you disables Recheck, you may get false positives."
msgstr ""

msgid "PGroonga supports CJK without changing source code."
msgstr ""

msgid ""
"PGroonga works without Recheck. PGroonga can find exact records only by index "
"search. PGroonga is fast for many hits case."
msgstr ""

msgid ""
"PGroonga doesn't support crash recovery and streaming replication because PGro"
"onga doesn't support WAL. Because PostgreSQL doesn't provide API for supportin"
"g WAL to extensions. PGroonga will support WAL when PostgreSQL provides the AP"
"I."
msgstr ""

msgid ""
"FYI: pg\\_trgm and pg\\_bigm support WAL. To be precise, GIN and GiST that are u"
"sed by pg\\_trgm and pg\\_bigm support WAL."
msgstr ""

msgid "## History"
msgstr ""

msgid ""
"PGroonga is based on [textsearch_groonga](http://textsearch-ja.projects.pgfoun"
"dry.org/textsearch_groonga.html) that was developed by Itagaki Takahiro. Thank"
"s for the works!"
msgstr ""

msgid "## The next step"
msgstr ""

msgid ""
"Interested? [Install](../install/) PGroonga and try [tutorial](../tutorial/). "
"You can understand more about PGroonga."
msgstr ""
44 changes: 44 additions & 0 deletions ja/overview/index.md
@@ -0,0 +1,44 @@
---
title: 概要
layout: ja
---

# 概要

PGroonga is a PostgreSQL extension. PGroonga provides a new index that uses [Groonga](http://groonga.org/).

Groonga is an embeddable super fast full text search engine. It can be embedded into MySQL. [Mroonga](http://mroonga.org/) is a storage engine that is based on Groonga. Groonga can also work as standalone search engine.

As default, PostgreSQL isn't capable for CJK full text search. But you can use super fast CJK full text search by installing PGroonga.

And more, PGroonga supports full text search against all text values in JSON. It's an unique feature. Built-in PostgreSQL features and [JsQuery](https://github.com/postgrespro/jsquery) don't support it.

## Related extensions

There are some extensions that implements CJK ready full text search:

* [pg_trgm](http://www.postgresql.org/docs/9.4/static/pgtrgm.html)
* It's bundled with PostgreSQL but it's not installed as default.
* You need to change pg\_trgm source code to support CJK.

* [pg_bigm](http://pgbigm.osdn.jp/)
* It supports CJK without changing source code.
* It requires [Recheck](http://pgbigm.osdn.jp/pg_bigm_en-1-1.html#enable_recheck) to remove false positives.
* Recheck is slow for many hits case. Because Recheck does sequential search against records found by index search.
* If you disables Recheck, you may get false positives.

PGroonga supports CJK without changing source code.

PGroonga works without Recheck. PGroonga can find exact records only by index search. PGroonga is fast for many hits case.

PGroonga doesn't support crash recovery and streaming replication because PGroonga doesn't support WAL. Because PostgreSQL doesn't provide API for supporting WAL to extensions. PGroonga will support WAL when PostgreSQL provides the API.

FYI: pg\_trgm and pg\_bigm support WAL. To be precise, GIN and GiST that are used by pg\_trgm and pg\_bigm support WAL.

## History

PGroonga is based on [textsearch_groonga](http://textsearch-ja.projects.pgfoundry.org/textsearch_groonga.html) that was developed by Itagaki Takahiro. Thanks for the works!

## The next step

Interested? [Install](../install/) PGroonga and try [tutorial](../tutorial/). You can understand more about PGroonga.

0 comments on commit 55b5850

Please sign in to comment.