PipelineDB currently supports PostgreSQL versions 10.1, 10.2, 10.3, 10.4, 10.5, and 11.0 on 64-bit architectures.
I don't know of any system similar to PipelineDB.
The utility of PipelineDB is to allow you to set up a system like ETL, without the need for a large infrastructure.
In other words, PipelineDB allows you to start data in one form and transform it into another form with SQL queries (When I talk about "other forms", it also means adding/deleting data with some joins, etc.).
For the risk of double insertion it is a more general problem than PipelineDB... When using a stream database, you will always have a risk of double insertions. It is either up to your program that sends the data to manage this, or you can fix the problem with a view (and the operator
I'm not sure I follow you....
My PipelineDB tables are also defined in my public schemas.
CREATE VIEW avg_of_forever AS SELECT AVG(x) FROM my_stream;
You can directly perform this task in your public schemas.
CREATE FOREIGN TABLE wiki_stream (
CREATE VIEW wiki_stats WITH (action=materialize) AS
SELECT hour, project,
count(*) AS total_pages,
sum(view_count) AS total_views,
min(view_count) AS min_views,
max(view_count) AS max_views,
avg(view_count) AS avg_views,
percentile_cont(0.99) WITHIN GROUP (ORDER BY view_count) AS p99_views,
sum(size) AS total_bytes_served
GROUP BY hour, project;
insert into wiki_stream values('now()','a','a',1,1);
select * into wiki_stats_tmp from wiki_stats_mrel ;
select pipelinedb.combine_table('wiki_stats', 'wiki_stats_tmp');
got error like this:
postgres=# select pipelinedb.combine_table('wiki_stats', 'wiki_stats_tmp');
ERROR: invalid string enlargement request size: -4