On 26 Jul 2001, Turbo Fredriksson wrote:
> > "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
>
> Would that be the 'debug_print_query = true' in posgresql.conf?
>
> It IS true, but still nothing in the syslog...
I'm not sure. But I expect the logging would go out the postmaster's logs,
not nec
> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
>> Is there a way to debug a PL/pgSQL function? It's behaving very
>> irradic!
Joel> It's crude, but you can output debugging statements w/ RAISE
Joel> NOTICE or catch flawed assumptions by RAISE EXCEPTION.
Tom> Also try tu
> Is there a way to debug a PL/pgSQL function? It's behaving very
> irradic!
> Joel> It's crude, but you can output debugging statements w/ RAISE
> Joel> NOTICE or catch flawed assumptions by RAISE EXCEPTION.
Also try turning on query logging, so you can see in the postmaster
log the que
On 25 Jul 2001, Turbo Fredriksson wrote:
> > "Joel" == Joel Burton <[EMAIL PROTECTED]> writes:
>
> Joel> On 25 Jul 2001, Turbo Fredriksson wrote:
> >> Is there a way to debug a PL/pgSQL function? It's behaving very
> >> irradic!
>
> Joel> It's crude, but you can output debug
On 25 Jul 2001, Turbo Fredriksson wrote:
> Is there a way to debug a PL/pgSQL function? It's behaving very irradic!
It's crude, but you can output debugging statements w/ RAISE NOTICE
or catch flawed assumptions by RAISE EXCEPTION.
--
Joel Burton <[EMAIL PROTECTED]>
Director of Information S
> "Joel" == Joel Burton <[EMAIL PROTECTED]> writes:
Joel> On 25 Jul 2001, Turbo Fredriksson wrote:
>> Is there a way to debug a PL/pgSQL function? It's behaving very
>> irradic!
Joel> It's crude, but you can output debugging statements w/ RAISE
Joel> NOTICE or catch flawe
Bill Shui wrote:
>Hi there,
>
> I remember that in earlier versions of Postgres.
> You have to do something (which I cannnot remember) to enable
> a user to create plpgsql functions.
>
> which versions of postgres were they?
>
>thanks in advance.
>
>Bill
>
CR