| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Richard Neill <rn214(at)richardneill(dot)org> |
| Cc: | 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 18:12:08 |
| Message-ID: | AANLkTinU5FwUNoGWtybEghbTw7_HH0msWrfeOfVtmsK+@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Mar 3, 2011 at 12:12 PM, Richard Neill <rn214(at)richardneill(dot)org> wrote:
> Do you not think it would be really amazingly useful? After all, in C, the
> single most useful debugging tool is "fprintf(stderr,...)", and yet
> postgresql doesn't have an equivalent that can operate on the most common
> data format. [I'm stretching the analogy a bit here, but it seems to me that
> a multi-row table is to postgresql as int is to C.]
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-03-03 18:31:55 | Re: BUG #5903: Turkish encoding problem |
| Previous Message | Tom Lane | 2011-03-03 18:05:31 | Re: BUG #5906: assertion failure in AtCleanup_Portals |