| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | "Jawarilal, Manish" <Manish(dot)Jawarilal(at)dell(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgbench bug / limitation |
| Date: | 2020-06-02 00:56:54 |
| Message-ID: | 513887.1591059414@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> ... I can't glean too much from the
> socket() documentation for either OS about what the return value is.
> I didn't see anything which indicated anything about how the return
> value is determined.
BTW, as far as that goes, POSIX is perfectly clear about this:
2.14. File Descriptor Allocation
All functions that open one or more file descriptors shall, unless
specified otherwise, atomically allocate the lowest numbered available
(that is, not already open in the calling process) file descriptor at
the time of each allocation.
It doesn't surprise me a lot to hear that Microsoft couldn't be
bothered to adhere to the spec, though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 鄭旭宏 | 2020-06-02 01:19:32 | Re: BUG #16472: Bug in to_timestamp ? |
| Previous Message | Tom Lane | 2020-06-02 00:21:27 | Re: pgbench bug / limitation |