Please Unsuscribe me.
Thanks.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
What about putting a "RAISE NOTICE" statement inside each of your child
functions ?
"Mario Splivalo" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Dobar dan! (Means 'good day' in Croatian)
>
> I have a postgres (plpgsql) function that calls other (plpgsql and sql)
> functions. T
On 1/10/06, Mario Splivalo <[EMAIL PROTECTED]> wrote:
The 'problem' is that, in the log file, I only see the top callingfunction, the one that client called. Is there a way to tell postgres tolog all the nested functions?smiply use:raise log ''
at the beginning of your functions.will work.depes
Dobar dan! (Means 'good day' in Croatian)
I have a postgres (plpgsql) function that calls other (plpgsql and sql)
functions. Those plpgsql functions then may call other plpsql or sql
functions.
The 'problem' is that, in the log file, I only see the top calling
function, the one that client calle
Hi, I got a third party utility to run pgsql in non administrative users account and without prompting password. The utility providers ensure that the utility will work in NT. I used this utility for running pg8.1.1 and it shows me the following error with a prompt titled "ININTDB.EXE - DLL Ini