[COMMITTERS] pgsql: Add outfuncs.c support for GatherPath.

[Robert Haas]

Add outfuncs.c support for GatherPath.

I dunno how commit 3bd909b220930f21d6e15833a17947be749e7fde missed
this, but it evidently did.

Branch
--
master

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

Modified Files
--
src/backend/nodes/outfuncs.c |   15 +++
1 file changed, 15 insertions(+)


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

Re: [COMMITTERS] pgsql: Generate parallel sequential scan plans in simple cases.

[David Fetter]

On Wed, Nov 11, 2015 at 02:03:05PM +, Robert Haas wrote:
> Generate parallel sequential scan plans in simple cases.

Yay!

Cheers,
David.
-- 
David Fetter  http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter  XMPP: david.fet...@gmail.com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate


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

Re: [COMMITTERS] pgsql: Generate parallel sequential scan plans in simple cases.

[Peter Geoghegan]

On Wed, Nov 11, 2015 at 7:35 AM, Magnus Hagander  wrote:
>> Congratulations!
>>
>
> +1. That's an exciting milestone!

Congratulations, Robert.


-- 
Peter Geoghegan


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

Re: [COMMITTERS] pgsql: Generate parallel sequential scan plans in simple cases.

[Magnus Hagander]

On Wed, Nov 11, 2015 at 4:32 PM, Simon Riggs  wrote:

> On 11 November 2015 at 14:03, Robert Haas  wrote:
>
>
>> Generate parallel sequential scan plans in simple cases.
>>
>
> Congratulations!
>
>
+1. That's an exciting milestone!

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

Re: [COMMITTERS] pgsql: Generate parallel sequential scan plans in simple cases.

[Simon Riggs]

On 11 November 2015 at 14:03, Robert Haas  wrote:


> Generate parallel sequential scan plans in simple cases.
>

Congratulations!

-- 
Simon Riggshttp://www.2ndQuadrant.com/

PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Re: [COMMITTERS] pgsql: Generate parallel sequential scan plans in simple cases.

[Robert Haas]

On Wed, Nov 11, 2015 at 10:35 AM, Magnus Hagander  wrote:
> On Wed, Nov 11, 2015 at 4:32 PM, Simon Riggs  wrote:
>> On 11 November 2015 at 14:03, Robert Haas  wrote:
>>> Generate parallel sequential scan plans in simple cases.
>> Congratulations!
>
> +1. That's an exciting milestone!

Thank you, both of you!  I'm pretty excited.

Needless to say, there is a ton of work left.  But I hope that getting
to this point will make it easier for other people to participate in
the work, or anyway, test.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


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

[COMMITTERS] pgsql: Make sequential scans parallel-aware.

[Robert Haas]

Make sequential scans parallel-aware.

In addition, this path fills in a number of missing bits and pieces in
the parallel infrastructure.  Paths and plans now have a parallel_aware
flag indicating whether whatever parallel-aware logic they have should
be engaged.  It is believed that we will need this flag for a number of
path/plan types, not just sequential scans, which is why the flag is
generic rather than part of the SeqScan structures specifically.
Also, execParallel.c now gives parallel nodes a chance to initialize
their PlanState nodes from the DSM during parallel worker startup.

Amit Kapila, with a fair amount of adjustment by me.  Review of previous
patch versions by Haribabu Kommi and others.

Branch
--
master

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

Modified Files
--
src/backend/commands/explain.c  |4 +
src/backend/executor/execAmi.c  |9 ++
src/backend/executor/execParallel.c |   54 ++--
src/backend/executor/nodeSeqscan.c  |  136 +++
src/backend/nodes/copyfuncs.c   |1 +
src/backend/nodes/outfuncs.c|2 +
src/backend/nodes/readfuncs.c   |1 +
src/backend/optimizer/path/allpaths.c   |2 +-
src/backend/optimizer/path/costsize.c   |   15 +++-
src/backend/optimizer/plan/createplan.c |   44 +-
src/backend/optimizer/plan/planner.c|2 +-
src/backend/optimizer/util/pathnode.c   |   29 ++-
src/include/executor/nodeSeqscan.h  |6 ++
src/include/nodes/execnodes.h   |   12 ++-
src/include/nodes/plannodes.h   |5 ++
src/include/nodes/relation.h|1 +
src/include/optimizer/cost.h|2 +-
src/include/optimizer/pathnode.h|2 +-
18 files changed, 254 insertions(+), 73 deletions(-)


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

[COMMITTERS] pgsql: Generate parallel sequential scan plans in simple cases.

[Robert Haas]

Generate parallel sequential scan plans in simple cases.

Add a new flag, consider_parallel, to each RelOptInfo, indicating
whether a plan for that relation could conceivably be run inside of
a parallel worker.  Right now, we're pretty conservative: for example,
it might be possible to defer applying a parallel-restricted qual
in a worker, and later do it in the leader, but right now we just
don't try to parallelize access to that relation.  That's probably
the right decision in most cases, anyway.

Using the new flag, generate parallel sequential scan plans for plain
baserels, meaning that we now have parallel sequential scan in
PostgreSQL.  The logic here is pretty unsophisticated right now: the
costing model probably isn't right in detail, and we can't push joins
beneath Gather nodes, so the number of plans that can actually benefit
from this is pretty limited right now.  Lots more work is needed.
Nevertheless, it seems time to enable this functionality so that all
this code can actually be tested easily by users and developers.

Note that, if you wish to test this functionality, it will be
necessary to set max_parallel_degree to a value greater than the
default of 0.  Once a few more loose ends have been tidied up here, we
might want to consider changing the default value of this GUC, but
I'm leaving it alone for now.

Along the way, fix a bug in cost_gather: the previous coding thought
that a Gather node's transfer overhead should be costed on the basis of
the relation size rather than the number of tuples that actually need
to be passed off to the leader.

Patch by me, reviewed in earlier versions by Amit Kapila.

Branch
--
master

Details
---
http://git.postgresql.org/pg/commitdiff/80558c1f5aa109d08db0fbd76a6d370f900628a8

Modified Files
--
src/backend/nodes/outfuncs.c  |1 +
src/backend/optimizer/path/allpaths.c |  190 -
src/backend/optimizer/path/costsize.c |2 +-
src/backend/optimizer/plan/planmain.c |   12 +++
src/backend/optimizer/plan/planner.c  |9 +-
src/backend/optimizer/util/clauses.c  |  183 +--
src/backend/optimizer/util/relnode.c  |   21 
src/backend/utils/cache/lsyscache.c   |   22 
src/include/nodes/relation.h  |1 +
src/include/optimizer/clauses.h   |2 +-
src/include/utils/lsyscache.h |1 +
11 files changed, 400 insertions(+), 44 deletions(-)


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

Re: [COMMITTERS] pgsql: Generate parallel sequential scan plans in simple cases.

[Michael Paquier]

On Thu, Nov 12, 2015 at 4:06 AM, Joe Conway  wrote:
> On 11/11/2015 10:54 AM, Robert Haas wrote:
>> On Wed, Nov 11, 2015 at 10:35 AM, Magnus Hagander  
>> wrote:
>>> On Wed, Nov 11, 2015 at 4:32 PM, Simon Riggs  wrote:
 On 11 November 2015 at 14:03, Robert Haas  wrote:
> Generate parallel sequential scan plans in simple cases.
 Congratulations!
>>>
>>> +1. That's an exciting milestone!
>>
>> Thank you, both of you!  I'm pretty excited.
>>
>> Needless to say, there is a ton of work left.  But I hope that getting
>> to this point will make it easier for other people to participate in
>> the work, or anyway, test.
>
> This is a huge milestone! Congratulations and many thanks for making it
> happen.

Yay.
-- 
Michael


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

[COMMITTERS] pgsql: Do a round of copy-editing on the 9.5 release notes.

[Tom Lane]

Do a round of copy-editing on the 9.5 release notes.

Also fill in the previously empty "major enhancements" list.  YMMV as to
which items should make the cut, but it's past time we had something more
than a placeholder here.

(I meant to get this done before beta2 was wrapped, but got distracted by
PDF build problems.  Better late than never.)

Branch
--
REL9_5_STABLE

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

Modified Files
--
doc/src/sgml/release-9.5.sgml |  271 +
1 file changed, 167 insertions(+), 104 deletions(-)


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

[COMMITTERS] pgsql: Do a round of copy-editing on the 9.5 release notes.

[Tom Lane]

Do a round of copy-editing on the 9.5 release notes.

Also fill in the previously empty "major enhancements" list.  YMMV as to
which items should make the cut, but it's past time we had something more
than a placeholder here.

(I meant to get this done before beta2 was wrapped, but got distracted by
PDF build problems.  Better late than never.)

Branch
--
master

Details
---
http://git.postgresql.org/pg/commitdiff/39b9978d9cac34ad799a5fa3ff3846f3e0372b0a

Modified Files
--
doc/src/sgml/release-9.5.sgml |  271 +
1 file changed, 167 insertions(+), 104 deletions(-)


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

[COMMITTERS] pgsql: Improve documentation around autovacuum-related storage paramete

[Tom Lane]

Improve documentation around autovacuum-related storage parameters.

These were discussed in three different sections of the manual, which
unsurprisingly had diverged over time; and the descriptions of individual
variables lacked stylistic consistency even within each section (and
frequently weren't in very good English anyway).  Clean up the mess, and
remove some of the redundant information in hopes that future additions
will be less likely to re-introduce inconsistency.  For instance I see
no need for maintenance.sgml to include its very own list of all the
autovacuum storage parameters, especially since that list was already
incomplete.

Branch
--
REL9_5_STABLE

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

Modified Files
--
doc/src/sgml/config.sgml   |   65 +++---
doc/src/sgml/maintenance.sgml  |   53 ++
doc/src/sgml/ref/create_table.sgml |  104 +++-
3 files changed, 106 insertions(+), 116 deletions(-)


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

[COMMITTERS] pgsql: Improve documentation around autovacuum-related storage paramete

[Tom Lane]

Improve documentation around autovacuum-related storage parameters.

These were discussed in three different sections of the manual, which
unsurprisingly had diverged over time; and the descriptions of individual
variables lacked stylistic consistency even within each section (and
frequently weren't in very good English anyway).  Clean up the mess, and
remove some of the redundant information in hopes that future additions
will be less likely to re-introduce inconsistency.  For instance I see
no need for maintenance.sgml to include its very own list of all the
autovacuum storage parameters, especially since that list was already
incomplete.

Branch
--
master

Details
---
http://git.postgresql.org/pg/commitdiff/6404751ce91fb02999e46700a1ac62b3c6319abf

Modified Files
--
doc/src/sgml/config.sgml   |   65 +++---
doc/src/sgml/maintenance.sgml  |   53 ++
doc/src/sgml/ref/create_table.sgml |  104 +++-
3 files changed, 106 insertions(+), 116 deletions(-)


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