From: | Kevin Burke <kev(at)inburke(dot)com> |
---|---|
To: | Michael Nolan <htfoot(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Debugging a function - what's the best way to do this quickly? |
Date: | 2017-12-19 19:47:55 |
Message-ID: | CAGs5PJLp=f938AVz-fx_JZpH4Ru67X+szAtfVS6ioQsFSAeo7A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Can you describe what you mean by log statements? I have log_statement
enabled and I can see the queries; the problem is the output is not logged
and not what I expect. I need to modify the function so it shows the output
of an intermediate CTE when I run it with specific inputs, and that's
currently a little cumbersome.
--
Kevin Burke
925.271.7005 | kev.inburke.com
On Tue, Dec 19, 2017 at 11:43 AM, Michael Nolan <htfoot(at)gmail(dot)com> wrote:
>
>
> On Tue, Dec 19, 2017 at 1:24 PM, Kevin Burke <kev(at)inburke(dot)com> wrote:
>
>> I'm writing a function that looks a little like this:
>>
>>
>> This seems pretty cumbersome. Is there an easier way I am missing?
>> Specifically it would be neat if it was easier to visualize the
>> intermediate steps in the query production. If there are professional tools
>> that help with this I would appreciate pointers to those as well.
>>
>> --
>> Kevin Burke
>> 925.271.7005 <(925)%20271-7005> | kev.inburke.com
>>
>
> Assuming it's not a function in production yet, put some log statements in
> it, then check the logs. If it's already in production, you'll probably
> have to create a separate version of the function for testing.
> --
> Mike Nolan
>
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2017-12-19 19:55:23 | Re: Debugging a function - what's the best way to do this quickly? |
Previous Message | Michael Nolan | 2017-12-19 19:43:35 | Re: Debugging a function - what's the best way to do this quickly? |