Re: TRUNCATE on foreign tables
Michael Paquier <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.devel.general |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jan 06, 2020 at 04:32:39PM -0500, Stephen Frost wrote: > 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. True enough. > 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..? Looking at the code, ExecuteTruncateGuts() passes down restart_seqs, so it sounds sensible to me to just pass down that to the FDW callback and the callback decide what to do. -- Michael
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl4ULSEACgkQnvQgOdby QH2pVQ/8DH7nHwcy1ukMLrmffVQwwBPVTRNqlRArqhIYXn92XjiY86Zp6ME0VUXM y0EZnaddZB1xfzvRgVGymoznNdPxLlHvU06FwLcP541UvrhzbyMuUmXTRe9BBzIb 0/BLSuGvQghoouXkUF4QO98GCJw/nAfDt1CIztAV3h4vg1a28uY41tvPudhK/rDg oIswT2iN2sY2MZK5BdeHjBcdVa02Pkjuz8mFhvUF6kdVO0VWjVuY0MhFNKScGmtg DKbAO+gIKh91troPz+n1BKtgDT1yXYo30wUP83+zQmcA0q8BDSlCpBuYrbc2ssLl CyiTepu3DrgqeGaRf8oxpjGKaV4Wf8OiZpIihseG5jRmkncraiwgI9hs1NgY2iWt Yh+D9Nf2retL0bngBJMnDALbeqRXLArHtpwqM6rfwTS2JL2VF+hBZ2u+23t2orqg vM6YYfGjZxODHlFZXx8p0Unx/77DiMWMSYRSVXqCuyoA3xkYwAET3UVI+HfUC7CS rU+YRSuaE+7ypBVh4kreIeRDps+6h2H9YsJ9i7bIFaTKjQSCVFm3C6RdG3CjDy0Q shZUL3p9rbolRzNge7omSrJBb77SwZt9JxgN/78zfwl5ASDHxl2BMceo02ftV+gE /dyRkTNV+UJVf2Oh1xzgk+M+zMJOzY1BXAvqTBq+qsBM95+bWEE= =pwmL -----END PGP SIGNATURE-----