On 18-10-2017 09:18, Ivan Sagalaev wrote:
Hello everyone,
An inaugural poster here, sorry if I misidentified a list for my
question.
I am planning to use PostgreSQL as a storage for application logs
(lines of text) with the following properties:
- Ingest logs at high rate: 3K lines per secon
Friendly greetings !
You may want to take a look at a postgresql "fork" called pipelinedb :
https://www.pipelinedb.com/
https://github.com/pipelinedb/pipelinedb
I'm not working for them, not using it, but i happen to know it exist :)
*hugs*
--
Laurent "ker2x" Laborde
I saw a similar project on oracle that was storing (long) messages (clob).
Partionning by creation date was in place, as btree indexes to access data
per id. It was working fine for inserts, as for sélect, but purges (delete)
where not freeing space. In fact rétention was not the same for all
rec
Can't get to hard data right now, but those are app logs that try to be
no more than ~100 bytes characters long for readability, and also HTTP
logs with long-ish request lines which might put it in the neighborhood
of 2K characters.
On 10/18/2017 02:30 AM, legrand legrand wrote:
What is the
What is the (min, max, avg) size of the inserted text ?
-
PAscal
SQLeo projection manager
Senior Oracle dba migrating towards PostgreSQL
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
