| From: | Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com> |
|---|---|
| To: | Marko Kreen <markokr(at)gmail(dot)com> |
| Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: segfault with plproxy |
| Date: | 2011-12-19 12:36:09 |
| Message-ID: | CAP_rwwmWPV-qDJG8h+g6DtTY6_sJDgC-zF1ukMuNw9HU6MmW5A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
W dniu 19 grudnia 2011 10:39 użytkownik Marko Kreen <markokr(at)gmail(dot)com> napisał:
> It seems you are making plproxy call public.list_users() recursively.
> Postgres probably OOM-s somewhere then.
I have log_statement='all' and the function is called only once:
2011-12-19 13:15:11 CET 20416 [local] testdb filip LOG: statement:
select * from list_users('%xyz%');
2011-12-19 13:15:11 CET 20400 LOG: server process (PID 20416) was
terminated by signal 11: Segmentation fault
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MURAT KOÇ | 2011-12-19 13:01:28 | Changing Passwords as Encrypted not Clear-Text |
| Previous Message | Filip Rembiałkowski | 2011-12-19 12:05:20 | Re: segfault with plproxy |