Re: BUG #5867: wish: plpgsql print table for debug

From: Merlin Moncure <mmoncure(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:35:22
Message-ID: AANLkTi=pE5t=L+qHRrgxxpQNO2OEXmm1HJeZw_Sqy=Ui@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Mar 3, 2011 at 12:37 PM, Richard Neill <rjn(at)richardneill(dot)org> wrote:
>
>> 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....

raise notice '%', (select array_to_string(array(select foo from foo), E'\n'));

:^).

merlin

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dimitri Fontaine 2011-03-03 20:53:41 Re: BUG #5867: wish: plpgsql print table for debug
Previous Message Pavel Stehule 2011-03-03 20:01:52 Re: BUG #5867: wish: plpgsql print table for debug