pgpipe error reporting - Mailing list pgsql-patches

From Magnus Hagander
Subject pgpipe error reporting
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE34BBEB@algol.sollentuna.se
Whole thread Raw
Responses Re: pgpipe error reporting  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
This patch updates pgpipe() on win32 to log exactly which part of the
call fails when it does. (As it is now, there is no way to figure out
the point of error). Shouldn't be a problem since it's most defintily
not a performance-critical path (only called on pgstat startup ATM).

This should help us debug the pipe error message that's on the win32
status page (which I myself have never been able to reproduce, and thus
haven't figured out a better way to debug yet)


/Magnus

 <<pipe_errmsg.patch>>

Attachment

pgsql-patches by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: [pgsql-hackers-win32] [HACKERS] select like...not using index
Next
From: Tom Lane
Date:
Subject: Re: [pgsql-hackers-win32] [HACKERS] select like...not using index