pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feednot english bug reports
3+ messages / 3 participants
[nested] [flat]
* not english bug reports
@ 2010-02-06 18:17 Jaime Casanova <jcasanov@systemguards.com.ec>
0 siblings, 0 replies; 3+ messages in thread
From: Jaime Casanova @ 2010-02-06 18:17 UTC (permalink / raw)
To: pgsql-docs
Hi,
^ permalink raw reply [nested|flat] 3+ messages in thread
* 42.6.8.1. Obtaining Information About An Error
@ 2020-10-07 17:50 PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2020-10-07 17:50 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: philippe.godfrin@nov.com
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/plpgsql-control-structures.html
Description:
42.6.8.1. Obtaining Information About An Error
This example omits raise notice code:
DECLARE
text_var1 text;
text_var2 text;
text_var3 text;
BEGIN
-- some processing which might cause an exception
...
EXCEPTION WHEN OTHERS THEN
GET STACKED DIAGNOSTICS text_var1 = MESSAGE_TEXT,
text_var2 = PG_EXCEPTION_DETAIL,
text_var3 = PG_EXCEPTION_HINT;
END;
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: 42.6.8.1. Obtaining Information About An Error
@ 2020-10-07 20:54 David G. Johnston <david.g.johnston@gmail.com>
parent: PG Doc comments form <noreply@postgresql.org>
0 siblings, 0 replies; 3+ messages in thread
From: David G. Johnston @ 2020-10-07 20:54 UTC (permalink / raw)
To: philippe.godfrin@nov.com, Pg Docs <pgsql-docs@lists.postgresql.org>
On Wed, Oct 7, 2020 at 12:57 PM PG Doc comments form <noreply@postgresql.org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/plpgsql-control-structures.html
> Description:
>
> 42.6.8.1. Obtaining Information About An Error
>
> This example omits raise notice code:
>
>
Yes, it does. I do not find the example any less useful for the lack.
How one chooses to use the error information is not the point of the
example, showing how to pull the data out of the error context is.
David J.
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2020-10-07 20:54 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-02-06 18:17 not english bug reports Jaime Casanova <jcasanov@systemguards.com.ec>
2020-10-07 17:50 42.6.8.1. Obtaining Information About An Error PG Doc comments form <noreply@postgresql.org>
2020-10-07 20:54 ` Re: 42.6.8.1. Obtaining Information About An Error David G. Johnston <david.g.johnston@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox