Tom Lane baebab3ace Allow IMPORT FOREIGN SCHEMA within pl/pgsql. ... Since IMPORT FOREIGN SCHEMA has an INTO clause, pl/pgsql needs to be aware of that and avoid capturing the INTO as an INTO-variables clause. This isn't hard, though it's annoying to have to make IMPORT a plpgsql keyword just for this. (Fortunately, we have the infrastructure now to make it an unreserved keyword, so at least this shouldn't break any existing pl/pgsql code.) Per report from Merlin Moncure. Back-patch to 9.5 where IMPORT FOREIGN SCHEMA was introduced. Report: <CAHyXU0wpHf2bbtKGL1gtUEFATCY86r=VKxfcACVcTMQ70mCyig@mail.gmail.com>		2016-07-12 18:07:03 -04:00
..
plperl	Translation updates	2016-06-20 09:48:08 -04:00
plpgsql	Allow IMPORT FOREIGN SCHEMA within pl/pgsql.	2016-07-12 18:07:03 -04:00
plpython	PL/Python: Report argument parsing errors using exceptions	2016-07-02 22:53:14 -04:00
tcl	Translation updates	2016-05-09 10:04:41 -04:00
Makefile	Make distprep and *clean build targets recurse into all subdirectories.	2011-07-03 13:55:12 -04:00