You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can see, this project hasn’t been updated for 8 years and it looks like the two issues that where opened in 2015 haven’t been investigated much.
I just checked and, as one could expect, it fails to build against PostgreSQL 13.
However, as far as I can see, it would look like a nice feature to have to be able to query a pg_dumped database through this foreign data wrapper.
Is there a reason why this project was abandoned?
Note that it is still referenced in https://wiki.postgresql.org/wiki/Foreign_data_wrappers.
The text was updated successfully, but these errors were encountered:
Hey @nboullis - this was abandoned mainly because I was the only person working on it, and I ended up switching roles and not having the time. It was developed for a specific use case, which it worked fine for. That didn't account for corner cases at all, which I expected people to run into and, hopefully, send a PR to fix. Nowadays, however, it would be pretty easy to write a newer one that uses pgdumplib via multicorn.
Hi,
As far as I can see, this project hasn’t been updated for 8 years and it looks like the two issues that where opened in 2015 haven’t been investigated much.
I just checked and, as one could expect, it fails to build against PostgreSQL 13.
However, as far as I can see, it would look like a nice feature to have to be able to query a pg_dumped database through this foreign data wrapper.
Is there a reason why this project was abandoned?
Note that it is still referenced in https://wiki.postgresql.org/wiki/Foreign_data_wrappers.
The text was updated successfully, but these errors were encountered: