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

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 b

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

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 b

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

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 s

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

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'

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

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'

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

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! >>

[COMMITTERS] pgsql: Be more noisy about "wrong number of nailed relations" initfile

Be more noisy about "wrong number of nailed relations" initfile problems. In commit 5d1ff6bd559ea8df1b7302e245e690b01b9a4fa4 I added some logic to relcache.c to try to ensure that the regression tests would fail if we made a mistake about which relations belong in the relcache init files. I'm quit

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

On Wed, Nov 11, 2015 at 9:08 AM, Peter Geoghegan wrote: > Congratulations, Robert. I should certainly extend my congratulations to Amit too. -- Peter Geoghegan -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgre

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

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 Remem

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

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

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

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, bo

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

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://w

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

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

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

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 applyi

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

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

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

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/n