From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Wim Bertels <wim(dot)bertels(at)khleuven(dot)be> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Error details in sql (and plpgsql) (possible feature request) |
Date: | 2011-06-22 08:48:02 |
Message-ID: | BANLkTi=AukwjnZZeTUkPO1J-nHia994Z0g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello
2011/6/22 Wim Bertels <wim(dot)bertels(at)khleuven(dot)be>:
> Hallo,
>
> Using libpqexec many error details can retrieved:
> http://www.postgresql.org/docs/8.4/interactive/libpq-exec.html
> (such as PG_DIAG_SEVERITY, PG_DIAG_MESSAGE_HINT,
> PG_DIAG_STATEMENT_POSITION.. as on the site above)
> eg:
> http://pgsql.privatepaste.com/656698b511
>
> but when u try to trap/catch all these errors,
> this doesnt seem possible from withing plpgsql,
> where we only have SQLSTATE and SQLERRM
> eg.
> http://www.postgresql.org/docs/current/interactive/plpgsql-control-structures.html
> http://pgsql.privatepaste.com/3b71488e8a
>
> So i think it would be interesting to be able to access the other error
> details as given by libpg-exec as well.
> Eg adding SEVERITY, MESSAGE_HINT, STATEMENT_POSITION, ..
> where we now only have SQLSTATE and SQLERRM
>
Patch for access to hint, detail, context is in process this commitfest.
Regards
Pavel Stehule
> mvg,
> Wim
>
>
>
> --
> 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 | Gavin Flower | 2011-06-22 08:53:19 | Re: unique across two tables |
Previous Message | Szymon Guz | 2011-06-22 08:38:58 | data compression in protocol? |