Re: [HACKERS] IMPORT FOREIGN SCHEMA can't be run in in pl/pgsql due to INTO

Merlin Moncure writes: > On Mon, Jul 11, 2016 at 3:09 PM, Tom Lane wrote: >> While we can certainly hack it by something along the lines of not >> recognizing INTO when the first token was IMPORT, the whole thing >> seems awfully messy and fragile. And it

Re: [HACKERS] IMPORT FOREIGN SCHEMA can't be run in in pl/pgsql due to INTO

On Mon, Jul 11, 2016 at 3:09 PM, Tom Lane wrote: > Merlin Moncure writes: >> Currently pl/pgsql interprets the mandatory INTO of IMPORT FOREIGN >> SCHEMA as INTO variable. > > Ugh, that's definitely a bug. > >> I estimate this to be minor oversight in >>

Re: [HACKERS] IMPORT FOREIGN SCHEMA can't be run in in pl/pgsql due to INTO

Merlin Moncure writes: > Currently pl/pgsql interprets the mandatory INTO of IMPORT FOREIGN > SCHEMA as INTO variable. Ugh, that's definitely a bug. > I estimate this to be minor oversight in > pl/pgsql parsing with respect to the introduction of this statement. While we

[HACKERS] IMPORT FOREIGN SCHEMA can't be run in in pl/pgsql due to INTO

Currently pl/pgsql interprets the mandatory INTO of IMPORT FOREIGN SCHEMA as INTO variable. I estimate this to be minor oversight in pl/pgsql parsing with respect to the introduction of this statement. Assuming it's easily fixed, would a patch to fix pl/pgsql parsing be accepted? merlin --