| From: | Marko Kreen <markokr(at)gmail(dot)com> |
|---|---|
| To: | Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com> |
| Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: segfault with plproxy |
| Date: | 2011-12-19 09:39:01 |
| Message-ID: | 20111219093901.GA20077@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Dec 17, 2011 at 10:25:40PM +0100, Filip Rembiałkowski wrote:
> Following scrip causes segmentation fault. Any ideas why / how to diagnose?
> create table part0.users( check(id%2=0) ) inherits (public.users);
> create table part1.users( check(id%2=1) ) inherits (public.users);
> create or replace function public.list_users(condition text)
> select * from public.list_users('%xyz%'); -- crash with segfault
It seems you are making plproxy call public.list_users() recursively.
Postgres probably OOM-s somewhere then.
Either move plproxy function to some other db, or use
TARGET/SELECT to pick different target function.
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marti Raudsepp | 2011-12-19 09:42:35 | Re: Logical Aggregate Functions (eg ANY()) |
| Previous Message | Misa Simic | 2011-12-19 09:35:25 | Re: indexes and tables |