Re: [PATCHES] fork/exec patch: pre-CreateProcess finalization

2003-12-28 Thread Claudio Natoli
[minor corrections (some duplication in arg passing); still under discussion/review] Cheers, Claudio > -Original Message- > From: Claudio Natoli [mailto:[EMAIL PROTECTED] > Sent: Saturday, 27 December 2003 9:27 PM > To: 'Tom Lane' > Cc: '[EMAIL PROTECTED]' > Subject: Re: [PATCHES] fork/e

[PATCHES] libpq endless loop if client_min_messages=debug1

2003-12-28 Thread Andreas Pflug
My Deja wrote: I am trying to get some query trees to appear in the PostgreSQL log and in order to that I have set client_min_messages = DEBUG1 in order to use the following settings debug_print_parse, debug_print_rewritten, or debug_print_plan which are required for the query tree to show up

Re: [PATCHES] libpq endless loop if client_min_messages=debug1

2003-12-28 Thread Tom Lane
Andreas Pflug <[EMAIL PROTECTED]> writes: > I reproduced this problem with 7.5 head backend and libpq under win32 > and Linux, and found that the problem is pqParseInput3 expecting a > message length >= 3 only for message types 'T', 'D' and 'd', but not > 'N'. Oops. Good catch.

Re: [PATCHES] libpq endless loop if client_min_messages=debug1

2003-12-28 Thread Tom Lane
Andreas Pflug <[EMAIL PROTECTED]> writes: > The attached patch fixes this. I wonder if there are additional message > types that might be longer? We should allow error messages to be long too, I guess, and I also added NOTIFY messages since there's no telling what people might try to do with the