From: | Leon Starr <leon_starr(at)modelint(dot)com> |
---|---|
To: | ashima athri <ashimaathri(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: How to 'print a table' in the middle of a plpgsql function |
Date: | 2011-01-31 21:51:52 |
Message-ID: | 02927557-3272-4A46-9BCC-EFF234435766@modelint.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Using Postgresql 8.4, I find that RAISE INFO does in fact print the stack to the psql console, just like
RAISE NOTICE and RAISE EXCEPTION.
On Jan 29, 2011, at 7:55 PM, ashima athri wrote:
>
> You can use RAISE INFO instead (it doesn't print the stack)
> http://www.postgresql.org/docs/7.4/static/plpgsql-errors-and-messages.html
>
> There is also a pgAdmin Debugger
> http://www.pgadmin.org/docs/1.8/debugger.html
>
>
> On Sun, Jan 30, 2011 at 1:19 AM, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> wrote:
> On 1/29/2011 12:59 AM, Leon Starr wrote:
> I am deep into debugging some pretty extensive plpgsql and it would be nice sometimes if I could somehow output the content of a table to the psql console at a particular point in a function.
>
> For example, I am executing a select that is not returning the expected row. So I am wondering, what exactly was in the table at the time the query was performed.
>
> Of course, I could just write a loop prior to my query with a bunch of raise notice statements, but I'll get a stack trace for each one. So that won't be pretty.
>
> Suggestions? Thx.
> Raise notice is PLPGSQL equivalent of DBMS_OUTPUT.PUT_LINE.
>
> --
> Mladen Gogala
> Sr. Oracle DBA
> 1500 Broadway
> New York, NY 10036
> (212) 329-5251
> www.vmsinfo.com
>
>
>
> --
> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | YAMAMOTO Takashi | 2011-01-31 23:39:24 | Re: [NOVICE] systable_getnext_ordered |
Previous Message | Tom Lane | 2011-01-31 17:07:36 | Re: handling concurrency right why am i wrong? |