Re: PG vs ElasticSearch for Logs

From: Thomas Güttler <guettliml(at)thomas-guettler(dot)de>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: PG vs ElasticSearch for Logs
Date: 2016-08-19 11:44:26
Message-ID: 68cf54f1-b9bd-7e35-7ab8-00a57105b79c@thomas-guettler.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Am 19.08.2016 um 12:44 schrieb Andreas Kretschmer:
> Thomas Güttler <guettliml(at)thomas-guettler(dot)de> wrote:
>
>>> How will you be using the logs? What kind of queries? What kind of searches?
>>> Correlating events and logs from various sources could be really easy with joins, count and summary operations.
>>
>> Wishes raise with possibilities. First I want to do simple queries about
>> hosts and timestamps. Then some simple substring matches.
>
> for append-only tables like this consider 9.5 and BRIN-Indexes for
> timestamp-searches. But if you deletes after N weeks BRIN shouldn't work
> properly because of vacuum and re-use of space within the table.
> Do you know BRIN?
>
> So, in your case, consider partitioning, maybe per month. So you can
> also avoid mess with table and index bloat.

Thank you very much for these hints. I did not know BRIN before.

> Greetings from Dresden to Chemnitz (is this still valid?)

Yes, I am in Chemnitz/Germany. Everything (kids, wife, friends, sports, job) is fine.

I hope the same with you?

Regards,
Thomas Güttler

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Verite 2016-08-19 13:20:08 Re: Sequential vs. random values - number of pages in B-tree
Previous Message Francisco Olarte 2016-08-19 10:59:40 Re: PG vs ElasticSearch for Logs