[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/commands/conversioncmds.c | 1 -
src/backend/commands/lockcmds.c   | 1 -
4 files changed, 4 deletions(-)


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[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.

It's been like this forever, so back-patch to all supported branches.

Report: 

Branch
--
REL9_2_STABLE

Details
---
http://git.postgresql.org/pg/commitdiff/7397f62e7fd9a90bba8c8dc8d61c569a41040762

Modified Files
--
src/interfaces/libpq/fe-exec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[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.

It's been like this forever, so back-patch to all supported branches.

Report: 

Branch
--
REL9_6_STABLE

Details
---
http://git.postgresql.org/pg/commitdiff/bb211b66f2934fbfe85c091dbff8db9ac520ceb5

Modified Files
--
src/interfaces/libpq/fe-exec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[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.

It's been like this forever, so back-patch to all supported branches.

Report: 

Branch
--
master

Details
---
http://git.postgresql.org/pg/commitdiff/886f6c5ccdb500c7e0abdf1500e20a304c45

Modified Files
--
src/interfaces/libpq/fe-exec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[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.

It's been like this forever, so back-patch to all supported branches.

Report: 

Branch
--
REL9_4_STABLE

Details
---
http://git.postgresql.org/pg/commitdiff/eb6bc03bfb43a11e15c2e24d9f6069add284f930

Modified Files
--
src/interfaces/libpq/fe-exec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[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.

It's been like this forever, so back-patch to all supported branches.

Report: 

Branch
--
REL9_1_STABLE

Details
---
http://git.postgresql.org/pg/commitdiff/fb6825fe57651dfd4dfe9d2041c715b03c5c6323

Modified Files
--
src/interfaces/libpq/fe-exec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[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.

It's been like this forever, so back-patch to all supported branches.

Report: 

Branch
--
REL9_5_STABLE

Details
---
http://git.postgresql.org/pg/commitdiff/4f87f7640981bae3a37e14bae744452e80e9545d

Modified Files
--
src/interfaces/libpq/fe-exec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[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.

It's been like this forever, so back-patch to all supported branches.

Report: 

Branch
--
REL9_3_STABLE

Details
---
http://git.postgresql.org/pg/commitdiff/455eaf9847ab0bb7a8dc6046be976053020c43bb

Modified Files
--
src/interfaces/libpq/fe-exec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[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 make the tests robust against platform
dependant ordering, add ORDER BYs guaranteeing the output order.

As it's possible that some of the changes expose platform dependant
ordering, push this earlier, to let the buildfarm shake out potentially
unstable results.

Discussion: <[email protected]>

Branch
--
master

Details
---
http://git.postgresql.org/pg/commitdiff/0137caf273f4297c4d36df3a542d7c0c853e75be

Modified Files
--
src/test/regress/expected/matview.out |   6 +-
src/test/regress/expected/psql.out|   2 +-
src/test/regress/expected/tsrf.out|   8 +--
src/test/regress/expected/union.out   | 129 ++
src/test/regress/expected/with.out|   8 +--
src/test/regress/sql/matview.sql  |   4 +-
src/test/regress/sql/psql.sql |   2 +-
src/test/regress/sql/tsrf.sql |   2 +-
src/test/regress/sql/union.sql|  63 +
src/test/regress/sql/with.sql |   8 +--
10 files changed, 123 insertions(+), 109 deletions(-)


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers


[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 clarify which SysV parameters need to be set with
an eye to total usage across all applications.

Branch
--
master

Details
---
http://git.postgresql.org/pg/commitdiff/3d21f08bccd316c3850a1943c1ee1e381dab1588

Modified Files
--
doc/src/sgml/runtime.sgml | 83 ---
1 file changed, 50 insertions(+), 33 deletions(-)


-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers