| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kai Kratz <kai(dot)kratz(at)googlemail(dot)com> |
| Cc: | andres(at)anarazel(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15327: postgres segfaults on ALTER FUNCTION ... SET SCHEMA ... |
| Date: | 2018-08-20 13:19:57 |
| Message-ID: | 19301.1534771197@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Kai Kratz <kai(dot)kratz(at)googlemail(dot)com> writes:
> It is an in-house developed FDW. Part of the surprise was that we
> execute the postgres integration tests (as described here:
> https://www.postgresql.org/docs/current/static/regress-run.html)
> against a postgres instance with our custom FDW loaded and no errors
> show up.
Well, actually, it *is* pretty surprising that an FDW would affect
the behavior of ALTER FUNCTION. Are you perhaps also hooking into
some parser hooks, or something else that's outside the FDW API?
Could you show us a backtrace from the segfault?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-08-20 13:24:48 | Re: BUG #15335: Documentation is wrong about archive_command and existing files |
| Previous Message | Igor Neyman | 2018-08-20 13:12:07 | RE: BUG #15340: FATAL ERROR: The application server could not be contacted. |