| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-committers(at)postgresql(dot)org" <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Add GET DIAGNOSTICS ... PG_CONTEXT in PL/PgSQL |
| Date: | 2013-07-25 03:13:31 |
| Message-ID: | CAOuzzgqzB0PYpvnUouaGYY4xFeoZbZc1VsrV8tzb64ea56n4UQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wednesday, July 24, 2013, Stephen Frost wrote:
> Still, if there's a reasonable way to collect the stack info without going
> through the error callbacks, without implementing a duplicate system, I'm
> all ears.
>
That said, I'll work on making this more independent of the error handling
and see if it can be made to use an independent memory context and try to
tighten it up to ensure it isn't called in an error case. Future callers
may try to.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-07-25 03:19:25 | Re: pgsql: Add GET DIAGNOSTICS ... PG_CONTEXT in PL/PgSQL |
| Previous Message | Tom Lane | 2013-07-25 03:12:00 | Re: pgsql: Add GET DIAGNOSTICS ... PG_CONTEXT in PL/PgSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-07-25 03:19:25 | Re: pgsql: Add GET DIAGNOSTICS ... PG_CONTEXT in PL/PgSQL |
| Previous Message | Tom Lane | 2013-07-25 03:12:00 | Re: pgsql: Add GET DIAGNOSTICS ... PG_CONTEXT in PL/PgSQL |