Re: BUG #15327: postgres segfaults on ALTER FUNCTION ... SET SCHEMA ... - Mailing list pgsql-bugs

From Kai Kratz
Subject Re: BUG #15327: postgres segfaults on ALTER FUNCTION ... SET SCHEMA ...
Date
Msg-id CAMJyv-4aMLee-YyzyEAzF9vCCnATrWd3zjWj3toznOE=B2MomA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15327: postgres segfaults on ALTER FUNCTION ... SET SCHEMA ...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #15327: postgres segfaults on ALTER FUNCTION ... SET SCHEMA...
List pgsql-bugs
Thanks for the very fast feedback,

It seems that I have an issue with an FDW extension that was loaded,
it didn't cross my mind that this could interfere with ALTER FUNCTION.
Same is true for the other 2 bug I filed a couple of minutes ago.

I am terribly sorry for creating unnecessary noise on pgsql-bugs. :(

Cheers
Kai Kratz
On Wed, Aug 15, 2018 at 3:41 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> =?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes:
> > pg-user=# CREATE SCHEMA test_schema;
> > CREATE SCHEMA
> > pg-user=# CREATE FUNCTION custom_eq(int, int)
> > RETURNS BOOL
> > LANGUAGE SQL IMMUTABLE AS
> > $$
> > SELECT $1 = $2;
> > $$;
> > CREATE FUNCTION
> > pg-user=# ALTER FUNCTION custom_eq(int, int) SET SCHEMA test_schema;
> > server closed the connection unexpectedly
>
> Huh.  Works fine for me.  Is the server you're using custom-built?
> If so, what build options did you use?  If not, where did you get
> it from?  In either case, the output of pg_config might be useful.
>
>                         regards, tom lane


pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15329: postgres segfaults on ALTER DOMAIN ... SET SCHEMA ...
Next
From: Andres Freund
Date:
Subject: Re: BUG #15327: postgres segfaults on ALTER FUNCTION ... SET SCHEMA...