PG vs ElasticSearch for Logs

From: Thomas Güttler <guettliml(at)thomas-guettler(dot)de>
To: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: PG vs ElasticSearch for Logs
Date: 2016-08-19 07:32:28
Message-ID: 012ae023-4ab8-40b0-265a-efd987dfd7b8@thomas-guettler.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2016-08-19 07:42:09 Re: PG vs ElasticSearch for Logs
Previous Message Victor Blomqvist 2016-08-19 06:25:50 Re: Limit Heap Fetches / Rows Removed by Filter in Index Scans