| From: | Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com> |
|---|---|
| To: | Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 'Magnus Hagander' <mha(at)sollentuna(dot)net>, "'pgsql-patches(at)postgresql(dot)org'" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: APC/socket fix (final?) |
| Date: | 2004-03-26 22:53:07 |
| Message-ID: | A02DEC4D1073D611BAE8525405FCCE2B55F3C9@harris.memetrics.local |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
> Tom Lane wrote:
> > What happens if the socket() call fails?
>
> Then we return in error. Refer to attachment.
Doh. You *were* referring to the attachment. Ok, so it'll need a check to
make sure the socket actually does get created, but this isn't a fatal flaw,
right? [is a work in progress I bashed out about 30 minutes ago].
I'm actually pretty hopeful over this patch, passes regression tests just
fine, lets us remove the win32_pgstat cruft, let's us easily mirror the unix
semantics, ...
Hopeless, or cute, work-around?
Cheers,
Claudio
---
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-03-26 22:57:09 | Re: APC/socket fix (final?) |
| Previous Message | Claudio Natoli | 2004-03-26 22:47:14 | Re: APC/socket fix (final?) |