Hi Alvaro, all > IMO this is a bad plan. It'll become _the_ way to run MERGE on foreign > tables, which will become a selling point for proprietary FDWs, and > nobody will be motivated to write the code to implement the long-term > plan you were describing. > > In short, -1 from me. >
I see your point, but this seems like an artificial limitation in Postgres. The parser usually doesn’t impose such restrictions, so it’s hard to understand why FDWs should be treated differently. If someone really wanted to work around this today, they could hack Postgres and avoid the limitation anyway. Our goal here is to follow the spirit of custom scans: enable experimentation and see what works. This approach doesn’t close the door to a more complete, native implementation later—it just creates a more natural path forward in the meantime. Thanks, Onder
