[COMMITTERS] pgsql: Remove some unnecessary #includes.

2016-10-10 Thread Heikki Linnakangas
Remove some unnecessary #includes. Amit Langote Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/6fb12cbcd6f1a971e113d7d32cc7ee920db4e097 Modified Files -- src/backend/commands/aggregatecmds.c | 1 - src/backend/commands/collationcmds.c | 1 - src/backend

[COMMITTERS] pgsql: In PQsendQueryStart(), avoid leaking any left-over async result.

2016-10-10 Thread Tom Lane
In PQsendQueryStart(), avoid leaking any left-over async result. Ordinarily there would not be an async result sitting around at this point, but it appears that in corner cases there can be. Considering all the work we're about to launch, it's hardly going to cost anything noticeable to check. I

[COMMITTERS] pgsql: In PQsendQueryStart(), avoid leaking any left-over async result.

2016-10-10 Thread Tom Lane
In PQsendQueryStart(), avoid leaking any left-over async result. Ordinarily there would not be an async result sitting around at this point, but it appears that in corner cases there can be. Considering all the work we're about to launch, it's hardly going to cost anything noticeable to check. I

[COMMITTERS] pgsql: In PQsendQueryStart(), avoid leaking any left-over async result.

2016-10-10 Thread Tom Lane
In PQsendQueryStart(), avoid leaking any left-over async result. Ordinarily there would not be an async result sitting around at this point, but it appears that in corner cases there can be. Considering all the work we're about to launch, it's hardly going to cost anything noticeable to check. I

[COMMITTERS] pgsql: In PQsendQueryStart(), avoid leaking any left-over async result.

2016-10-10 Thread Tom Lane
In PQsendQueryStart(), avoid leaking any left-over async result. Ordinarily there would not be an async result sitting around at this point, but it appears that in corner cases there can be. Considering all the work we're about to launch, it's hardly going to cost anything noticeable to check. I

[COMMITTERS] pgsql: In PQsendQueryStart(), avoid leaking any left-over async result.

2016-10-10 Thread Tom Lane
In PQsendQueryStart(), avoid leaking any left-over async result. Ordinarily there would not be an async result sitting around at this point, but it appears that in corner cases there can be. Considering all the work we're about to launch, it's hardly going to cost anything noticeable to check. I

[COMMITTERS] pgsql: In PQsendQueryStart(), avoid leaking any left-over async result.

2016-10-10 Thread Tom Lane
In PQsendQueryStart(), avoid leaking any left-over async result. Ordinarily there would not be an async result sitting around at this point, but it appears that in corner cases there can be. Considering all the work we're about to launch, it's hardly going to cost anything noticeable to check. I

[COMMITTERS] pgsql: In PQsendQueryStart(), avoid leaking any left-over async result.

2016-10-10 Thread Tom Lane
In PQsendQueryStart(), avoid leaking any left-over async result. Ordinarily there would not be an async result sitting around at this point, but it appears that in corner cases there can be. Considering all the work we're about to launch, it's hardly going to cost anything noticeable to check. I

[COMMITTERS] pgsql: Make regression tests less dependent on hash table order.

2016-10-10 Thread Andres Freund
Make regression tests less dependent on hash table order. Upcoming changes to the hash table code used, among others, for grouping and set operations will change the output order for a few queries. To make it less likely that actual bugs are hidden between regression test ordering changes, and to

[COMMITTERS] pgsql: Update user docs for switch to POSIX semaphores.

2016-10-10 Thread Tom Lane
Update user docs for switch to POSIX semaphores. Since commit ecb0d20a9 hasn't crashed and burned, here's the promised docs update for it. In addition to explaining that Linux and FreeBSD ports now use POSIX semaphores, I did some wordsmithing on pre-existing wording; in particular trying to clar