Thread: pgpipe error reporting

pgpipe error reporting

From
"Magnus Hagander"
Date:
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

Re: pgpipe error reporting

From
Bruce Momjian
Date:
Patch applied.  Thanks.

---------------------------------------------------------------------------


Magnus Hagander wrote:
> 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>>

Content-Description: pipe_errmsg.patch

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073