From: Tomas Vondra <tomas.von...@2ndquadrant.com> > I'm not sure when I'll have time to work on this again, so if you are > interested and willing to work on it, please go ahead. I'll gladly do > reviews and help you with it.
Thank you very much. > I think transferring data to other databases is fine - interoperability > is a big advantage for users, I don't see it as something threatening > the PostgreSQL project. I doubt this would make it more likely for users > to migrate from PostgreSQL - there are many ways to do that already. Definitely true. Users may want to use INSERT SELECT to do some data transformation in their OLTP database and load it into a non-Postgres data warehouse. > Yeah. I think handling complete failure should not be very difficult, > but there are cases that worry me more. For example, what if there's a > before trigger (on the remote db) that "skips" inserting some of the > rows by returning NULL? > Yeah. I wonder if the FDW needs to indicate which features are supported > by the ExecForeignMultiInsert, e.g. by adding a function that decides > whether batch insert is supported (it might also do that internally by > calling ExecForeignInsert, of course). Thanks for your advice. I'll try to address them. Regards Takayuki Tsunakawa
