couchdb_fdw icon indicating copy to clipboard operation
couchdb_fdw copied to clipboard

Published 20 hours ago • verified publisher icon ZhengYang

Updated status

Open brandonzylstra opened this issue 11 years ago • 3 comments

The README says

IMPORTANT: There're bugs in the existing version. I'm working on it and will be releasing another version very soon.

Apparently you've abandoned the project, because there haven't been any updates in 3 years. OR: maybe you fixed the bugs and just forgot to update the README. It would be helpful either way to update the README with the actual status.

brandonzylstra avatar Aug 26 '14 16:08 brandonzylstra

I have started a project which provides something similar: https://github.com/sysadminmike/couch-to-postgres

sysadminmike avatar Dec 19 '14 12:12 sysadminmike

@sysadminmike Your README seems to be implying that an FDW would not give immediate updates. Is that correct? Can you give any more details on how your approach differs from a FDW, and why/when it would be better or worse? Thanks.

brandonzylstra avatar Dec 22 '14 16:12 brandonzylstra

What i have done is to watch couch change log and update a table in postgres with the couch doc.

It lets postgres query a local near real time copy of the couch database - you can add indexes to it as well.

Any inserts/updates/deletes are sent to the couch server and then streamed back into postgres.

It is similar to: https://github.com/elasticsearch/elasticsearch-river-couchdb but for postgres

sysadminmike avatar Dec 22 '14 16:12 sysadminmike