Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: statistics process shutting down


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
  • Cc: "Win 32 hackers PGSQL" <pgsql-hackers-win32(at)postgresql(dot)org>
  • Subject: Re: statistics process shutting down
  • Date: Tue, 30 Nov 2004 15:45:04 -0500
  • Message-id: <24231(dot)1101847504(at)sss(dot)pgh(dot)pa(dot)us>

"Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> if (ret < 0)
> {
>    int  wsa_errno;
>    wsa_errno = WSAGetLastError();

>    if (WSAECONNRESET == wsa_errno)
>    {   /* EOF on the pipe! (win32 socket based implementation) */
>       ret = 0;
>    }
>    else
>    {
>       errno = wsa_errno;  /* this *might* be ok */
>    }
> }

> Maybe Magnus might comment here.  This doesn't explain why the read call
> is failing but I'm pretty sure the error code is not being properly
> returned.

I recall a lot of angst about whether the encoding of WSAGetLastError()
is compatible with errno values, but I forget what the conclusion was.
Can we just assign to errno like that, or do we need a mapping function?

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group