Patrick Welche <[EMAIL PROTECTED]> writes:
> ... I was running postmaster -d4, yet the only
> query I saw was the last LOG one. I pretty sure that I would see all queries
> with -d3 before..
It looked to me like you were just running with the recently-added
frill to log only queries that cause er
Tom Lane wrote:
> Patrick Welche <[EMAIL PROTECTED]> writes:
> > ... I was running postmaster -d4, yet the only
> > query I saw was the last LOG one. I pretty sure that I would see all queries
> > with -d3 before..
>
> It looked to me like you were just running with the recently-added
> frill to
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> (Looks at code...) Ah. It looks like -d to the postmaster no longer
>> means anywhere near what it used to. Bruce --- compare the handling
>> of -d in the backend (postgres.c lines 1251ff) with its handling in
>> the postmaster (pos
Uh, yes, it is a little confusing and I am not sure that patch is right
anymore. I haven't applied it.
Another issue is that we used to have a global debug_level variable that was
propogated to the client. Now, we just have the GUC value which does
propogate like the global one did. Does the p
Bruce Momjian <[EMAIL PROTECTED]> writes:
> ... Now, we just have the GUC value which does
> propogate like the global one did. Does the postmaster still pass -dX
> down to the child like it used to?
Evidently not; else Patrick wouldn't be complaining that it doesn't
work like it used to.
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > ... Now, we just have the GUC value which does
> > propogate like the global one did. Does the postmaster still pass -dX
> > down to the child like it used to?
>
> Evidently not; else Patrick wouldn't be complaining that it doesn't
Bruce Momjian <[EMAIL PROTECTED]> writes:
> diff -c -c -r1.294 postgres.c
> *** src/backend/tcop/postgres.c25 Sep 2002 20:31:40 -1.294
> --- src/backend/tcop/postgres.c26 Sep 2002 05:15:41 -
> ***
> *** 1281,1288
>* -d 0 allows user
