This is the main PostgreSQL git repository. http://git.postgresql.org/cgit/postgresql.git/atom?h=master 2022-08-13T21:53:28Z 2022-08-13T21:53:28Z Thomas Munro 2022-08-13T21:53:28Z urn:sha1:5579388d2dda60ded329a4623f9b4529e91a1b24 SUSv3, all targeted Unixes and modern Windows have getaddrinfo() and related interfaces. Drop the replacement implementation, and adjust some headers slightly to make sure that the APIs are visible everywhere using standard POSIX headers and names. Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/CA%2BhUKG%2BL_3brvh%3D8e0BW_VfX9h7MtwgN%3DnFHP5o7X2oZucY9dg%40mail.gmail.com 2022-01-08T00:04:57Z Bruce Momjian 2022-01-08T00:04:57Z urn:sha1:27b77ecf9f4d5be211900eda54d8155ada50d696 Backpatch-through: 10 2021-01-02T18:06:25Z Bruce Momjian 2021-01-02T18:06:25Z urn:sha1:ca3b37487be333a1d241dab1bbdd17a211a88f43 Backpatch-through: 9.5 2020-01-01T17:21:45Z Bruce Momjian 2020-01-01T17:21:45Z urn:sha1:7559d8ebfa11d98728e816f6b655582ce41150f3 Backpatch-through: update all files in master, backpatch legal files through 9.4 2019-05-22T17:04:48Z Tom Lane 2019-05-22T17:04:48Z urn:sha1:8255c7a5eeba8f1a38b7a431c04909bde4f5e67d Switch to 2.1 version of pg_bsd_indent. This formats multiline function declarations "correctly", that is with additional lines of parameter declarations indented to match where the first line's left parenthesis is. Discussion: https://postgr.es/m/CAEepm=0P3FeTXRcU5B2W3jv3PgRVZ-kGUXLGfd42FFhUROO3ug@mail.gmail.com 2019-01-02T17:44:25Z Bruce Momjian 2019-01-02T17:44:25Z urn:sha1:97c39498e5ca9208d3de5a443a2282923619bf91 Backpatch-through: certain files through 9.4 2018-01-03T04:30:12Z Bruce Momjian 2018-01-03T04:30:12Z urn:sha1:9d4649ca49416111aee2c84b7e4441a0b7aa2fac Backpatch-through: certain files through 9.3 2017-06-21T19:19:25Z Tom Lane 2017-06-21T19:18:54Z urn:sha1:c7b8998ebbf310a156aa38022555a24d98fdbfb4 Change pg_bsd_indent to follow upstream rules for placement of comments to the right of code, and remove pgindent hack that caused comments following #endif to not obey the general rule. Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using the published version of pg_bsd_indent, but a hacked-up version that tried to minimize the amount of movement of comments to the right of code. The situation of interest is where such a comment has to be moved to the right of its default placement at column 33 because there's code there. BSD indent has always moved right in units of tab stops in such cases --- but in the previous incarnation, indent was working in 8-space tab stops, while now it knows we use 4-space tabs. So the net result is that in about half the cases, such comments are placed one tab stop left of before. This is better all around: it leaves more room on the line for comment text, and it means that in such cases the comment uniformly starts at the next 4-space tab stop after the code, rather than sometimes one and sometimes two tabs after. Also, ensure that comments following #endif are indented the same as comments following other preprocessor commands such as #else. That inconsistency turns out to have been self-inflicted damage from a poorly-thought-through post-indent "fixup" in pgindent. This patch is much less interesting than the first round of indent changes, but also bulkier, so I thought it best to separate the effects. Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us 2017-06-21T18:39:04Z Tom Lane 2017-06-21T18:39:04Z urn:sha1:e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 The new indent version includes numerous fixes thanks to Piotr Stefaniak. The main changes visible in this commit are: * Nicer formatting of function-pointer declarations. * No longer unexpectedly removes spaces in expressions using casts, sizeof, or offsetof. * No longer wants to add a space in "struct structname *varname", as well as some similar cases for const- or volatile-qualified pointers. * Declarations using PG_USED_FOR_ASSERTS_ONLY are formatted more nicely. * Fixes bug where comments following declarations were sometimes placed with no space separating them from the code. * Fixes some odd decisions for comments following case labels. * Fixes some cases where comments following code were indented to less than the expected column 33. On the less good side, it now tends to put more whitespace around typedef names that are not listed in typedefs.list. This might encourage us to put more effort into typedef name collection; it's not really a bug in indent itself. There are more changes coming after this round, having to do with comment indentation and alignment of lines appearing within parentheses. I wanted to limit the size of the diffs to something that could be reviewed without one's eyes completely glazing over, so it seemed better to split up the changes as much as practical. Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us 2017-04-11T13:22:21Z Magnus Hagander 2017-04-11T13:21:25Z urn:sha1:a4777f35565b80ae10605d6d417e5d173156f7da This used to mean "Visual C++ except in those parts where Borland C++ was supported where it meant one of those". Now that we don't support Borland C++ anymore, simplify by using _MSC_VER which is the normal way to detect Visual C++.