>> ISTM this would be better off waiting until we turn large parts of
>> pg_dump into a library, as has been often discussed, at which point it
>> should be relatively simple to write a custom client to do what the OP
>> wants. I agree that it does not at all belong in pg_dump.
> I can't imagine many of my clients ever writing another C program or even
> being willing to pay me to do so. While modularizing pg_dump is a fine idea,
> I don't think it addresses the same set of use cases and users as this
It's not clear to me that your use case is very compelling. Does your
foreign database not support import via CSV or XML? Postgres can now
produce both of these for any arbitrary query.
Sent via pgsql-patches mailing list (email@example.com)
To make changes to your subscription: