| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Richard Neill <rjn(at)richardneill(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Richard Neill <rn214(at)richardneill(dot)org>, Richard Neill <postgresql(at)richardneill(dot)org>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5867: wish: plpgsql print table for debug |
| Date: | 2011-03-03 20:01:52 |
| Message-ID: | AANLkTimOtW2p3kaUpSeF8vH7wOLORHv2akj1W_kiAfSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
2011/3/3 Richard Neill <rjn(at)richardneill(dot)org>:
>
>> Sure it does. You can pass the tuple to RAISE NOTICE easily enough.
>> It won't have all the same bells and whistles psql would supply, but
>> it prints out well enough for debugging. Or at least it's never
>> bothered me.
>
> Sorry if I'm being dense, but I can't see how you can pass a tuple; I think
> raise-notice only lets you pass individual strings/integers. But I don't
> think we can pass all of them without specifying in advance how many there
> are....
yes, it's possible for ROW or RECORD datatype
Regards
Pavel Stehule
>
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2011-03-03 20:35:22 | Re: BUG #5867: wish: plpgsql print table for debug |
| Previous Message | Christian Kastner | 2011-03-03 19:47:42 | Possible regression: libpq + SSL aborts when user has no home directory |