From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Seb <spluque(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: debugging functions |
Date: | 2014-03-12 19:35:27 |
Message-ID: | CAFj8pRDoNqGh1jpULqre4A+KNhEiooxV_HizHJKumjiUNwa9DA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello
I don't know any tool that can do what you want. You can write your
function as fault tolerant - you can trap errors, and you can print a some
messages.
That is all what is possible
Regards
Pavel
2014-03-12 20:29 GMT+01:00 Seb <spluque(at)gmail(dot)com>:
> Hi,
>
> I am aware of the edb-debugger that one can use with pgadmin for
> debugging functions. However, I am looking for a solution that doesn't
> involve such additions to the server. I'm using a function in a SELECT
> query, but it's failing for some rows in a very large table. By using
> LIMIT and OFFSET I see that it runs fine for some parts of the table.
> Is there some way to print the rows where it fails? For now, I've
> simply modified the function to return a value that I can use in the
> SELECT query to filtering, but I'm wondering whether there's a parameter
> or setting that would accomplish the same thing without modifying the
> function.
>
> Thanks,
>
> --
> Seb
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Welton | 2014-03-12 20:34:00 | Re: named queries and the wire protocol |
Previous Message | Seb | 2014-03-12 19:29:42 | debugging functions |