Re:Running 10M PostgreSQL Indexes in Production
by vijayparashar12 on Tuesday June 13, 2017 @04:05AM
(#14543472)
Good to know about the partial indexes on Postgres, but I am little queries to ask you as an analytics company your system is write-heavy system, how did you justify increasing latency of writes, I am pretty sure that you have some kind of queue in front of Postgres to overcome this problem, secondly what I understand from the blog and nature of event-based analytics it's generally time series data, What made you stick to Postgres where I can easily see lot of different datastores build specifically to deal with time series data like Elasticsearch and influxDB ? can you give me some insights on why Postgres.
[ Parent
| on HN ]
Re:Running 10M PostgreSQL Indexes in Production
by macobo on Tuesday June 13, 2017 @04:11AM
(#14543483)
You need a queue in front of your database irregardless of write latency. Otherwise you tie your availability to database availability as downtime (even for upgrades) is often unavoidable and network problems are common.
Dan gave a pretty good talk about the high-level details of how/why postgres a couple of years back: https://www.youtube.com/watch?v=NVl9_6J1G60.
One reason of why pg is that SQL is really powerful for building complex queries.