On Fri, Sep 29, 2017 at 10:19:03PM +0200, David Fetter wrote: > On Fri, Sep 29, 2017 at 01:47:59PM -0400, Tom Lane wrote: > > Konstantin Knizhnik <k.knizh...@postgrespro.ru> writes: > > > According to Postgresql documentation it is not possible to alter server > > > for foreign table: > > > https://www.postgresql.org/docs/10/static/sql-alterforeigntable.html > > > > Hmm, we'd have to check if the table's options were legal for the > > new FDW, but in principle we could support this, I suppose. > > Not sure if it's useful enough to be worth the trouble. > > It would definitely be useful if it were available. Nodes are a good > bit more fungible than they were even 5 years back.
It would be nice to have DDLs for everything ALTERation that one could make that is trivial to support. It would also be nice to have a rule that every DDL (and every ADD/DROP in ALTER statements) support IF EXISTS / IF NOT EXISTS, and, where meaningful, OR REPLACE. I work around a lot of missing IE/INE/OR by using techniques like: conditioning on a schema query, using DROP IF EXISTS then CREATE in a transaction (when the DROP has IE but the CREATE does not have INE), catching exceptions, and so on. These are little things -- quality of life sorts of things :) I've also grown accustomed to writing complex pg_catalog queries. It'd be nice to have some built-in views on the pg_catalog -- something better than the information_schema. I have written some that we use for code generation based on PG schemas; we'd be glad to contribute them. Nico -- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
