Making Postgres Bloom

Re:Making Postgres Bloom by ahachete on Thursday July 30, 2015 @03:28PM (#9977370)

usman-m, the approach of PipelineDB seems really interesting. However, I'd like to understand how in your opinion it compares with processing the stream of data changes accessed over PostgreSQL's logical decoding (http://www.postgresql.org/docs/9.4/static/logicaldecoding.ht...) interface. Thank you

[ Parent | on HN ]

Re:Making Postgres Bloom by usman-m on Thursday July 30, 2015 @03:50PM (#9977513)

ahachete, I'm not sure if I totally understand your question.

Continuous views are consumers for streams. You can think of them as high throughput real-time materialized views. The source of data for the stream can be practically anything. Logical decoding on the other hand is a producer of streaming data--it's basically a human readable replication log. So you could potentially stream the logically decoded log into PipelineDB and build some continuous views in front of it.

[ Parent | on HN ]

Re:Making Postgres Bloom by ahachete on Thursday July 30, 2015 @07:43PM (#9979027)

I was thinking of a system where data is extracted from the source database and then the (changes) data are processed real-time by a software that consumes this stream. So other than the obvious differences (need to write the software, SQL support) what would be the real advantage of using PipelineDB over a system with PostgreSQL+logical decoding+stream processing of that data?

Thanks!

[ Parent | on HN ]