Re: segfault with plproxy
| От | Marko Kreen |
|---|---|
| Тема | Re: segfault with plproxy |
| Дата | |
| Msg-id | 20111219093901.GA20077@gmail.com обсуждение исходный текст |
| Ответ на | segfault with plproxy (Filip Rembiałkowski <filip.rembialkowski@gmail.com>) |
| Ответы |
Re: segfault with plproxy
Re: segfault with plproxy |
| Список | 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
В списке pgsql-general по дате отправления: