Re: TRUNCATE on foreign tables
Stephen Frost <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.devel.general |
|---|---|
| Message-ID | <[email protected]> |
Greetings, * Michael Paquier ([email protected]) wrote: > On Thu, Jan 02, 2020 at 09:46:44AM -0500, Stephen Frost wrote: > > I agree that the FDW callback should support multiple tables in the > > TRUNCATE, but I think it also should include CASCADE as an option and > > have that be passed on to the FDW to handle. > > As much as RESTRICT, ONLY and the INDENTITY clauses, no? Just think > about postgres_fdw. RESTRICT, yes. I don't know about ONLY being sensible as we don't really deal with inheritance and foreign tables very cleanly today, as I said up-thread, so I'm not sure if we really want to put in the effort that it'd require to figure out how to make ONLY make sense. The question about how to handle IDENTITY is a good one. I suppose we could just pass that down and let the FDW sort it out..? Thanks, Stephen
signature.asc
(application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJeE6d2AAoJEO1sijiDR2RV92IP/A3CVEanLputUSDsK9bwvhhO YzqRnDchBAXtfUNmUyNe0IDPK3VO9LCPr9LNebE7q+pIVM+wsTf4p8RWbHnIfbzS yTwvON6ZTX6rkh3P0ITv4XU8j7F2LjV17XWiRYQyXWymNmLvea5nKHE7U94FKRg9 jvTkrL4xzaB+MY8uZTtTLGdBnErJuMcDoe6mYhJe1emE9pFGhbo8PdxkMFiNG8wX ftFebbW5uVN78tUQXf7qgaJw6fgmPExm+wCnR30KzkSOa7Gpbpip+kHGkkfqsJ2N puH7IA/JV5Fbs2Z3b6dOVRH0n9VfNpQVPdfBt6fef71cNp/7WPGduuf1cdFVsC+/ Pd/hXTr3G0QHP7TqruagpqwwkYfH4nFffNYXxP4G1VakfIJrPWBUK2r4c2MbK1L6 3iofLhfXRHOvs56dN+X8NusO5Xtkt6XQ9d1R4qmv94DxxnxRqFSo2eEn6TFmKF4G P/63QojzK73gy1iDluwdfA06f9Gy2vOyID3pCzh8p/DsAG1JKsrStQw4uHdqWPAh gdPpLz11ko6FcSaJiHKotdezv7cy/yHJNH/HCnCHjLHYofdlA62ou6/wHrV7Noi9 7dSggLAdFk6fQ8N/8wt+e0oVAQyEH2/tKy/C62zGq+iSLpehckonWyI6CNx8qKOP Vg0Qww6qsyvfysbwAP3q =FsTm -----END PGP SIGNATURE-----