Re: [HACKERS][PATCH] adding simple sock check for windows
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: CharSyam <charsyam@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-04-01T05:30:07Z
Lists: pgsql-hackers
Amit Kapila <amit.kapila16@gmail.com> writes: > oops, I just saw that you have already pushed a fix for it. I am not > sure if we should try to do anything about walrcv_receive's output > still uses pgsocket instead of int as the usage in itself doesn't have > any problem. I see a few places where we're still assigning PQsocket's result to a pgsocket variable, but none of them are worrying about the possibility that it's not a valid socket, and I'm not sure they need to. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix assorted issues in parallel vacuumdb.
- ba0c65ab0922 9.5.13 landed
- 94173d3eeb44 11.0 landed
- 80bfdc0ccda0 10.4 landed
- 6cd110c477b4 9.6.9 landed