PG vs ElasticSearch for Logs

Поиск
Список
Период
Сортировка
От Thomas Güttler
Тема PG vs ElasticSearch for Logs
Дата
Msg-id 012ae023-4ab8-40b0-265a-efd987dfd7b8@thomas-guettler.de
обсуждение исходный текст
Ответы Re: PG vs ElasticSearch for Logs  (John R Pierce <pierce@hogranch.com>)
Re: PG vs ElasticSearch for Logs  (Merlin Moncure <mmoncure@gmail.com>)
Re: PG vs ElasticSearch for Logs  (Andy Colson <andy@squeakycode.net>)
Список pgsql-general
I want to store logs in a simple table.

Here my columns:

   Primary-key (auto generated)
   timestamp
   host
   service-on-host
   loglevel
   msg
   json (optional)

I am unsure which DB to choose: Postgres, ElasticSearch or ...?

We don't have high traffic. About 200k rows per day.

My heart beats for postgres. We use it since several years.

On the other hand, the sentence "Don't store logs in a DB" is
somewhere in my head.....

What do you think?



--
Thomas Guettler http://www.thomas-guettler.de/


В списке pgsql-general по дате отправления:

Предыдущее
От: Victor Blomqvist
Дата:
Сообщение: Re: Limit Heap Fetches / Rows Removed by Filter in Index Scans
Следующее
От: John R Pierce
Дата:
Сообщение: Re: PG vs ElasticSearch for Logs