On Sat, Mar 4, 2017 at 12:45 PM, Michael Paquier
wrote:
> On Sat, Mar 4, 2017 at 3:43 PM, Robert Haas wrote:
>> Fix the optimization to skip WAL-logging on table created in the same
>> transaction (originally submitted to CommitFest 2016-03)
>>
On Sat, Mar 4, 2017 at 3:43 PM, Robert Haas wrote:
> Fix the optimization to skip WAL-logging on table created in the same
> transaction (originally submitted to CommitFest 2016-03)
> https://commitfest.postgresql.org/13/528/
> Michael perhaps-unwisely set the committer on
On Fri, Mar 3, 2017 at 10:43 PM, Robert Haas wrote:
> Parallel tuplesort (originally submitted to CommitFest 2016-09)
> https://commitfest.postgresql.org/13/690/
> Heikki and I have both done a little work to move this forward, but it
> needs a lot more attention than it
On Thu, Mar 2, 2017 at 6:58 AM, Tom Lane wrote:
> Indeed. As usual, a depressingly large number of patches appeared out of
> the woodwork in the last few days before the deadline, and more than a
> couple of those seem to be clear violations of our rule about "no major
> new
Thomas Munro writes:
> On Thu, Mar 2, 2017 at 4:42 AM, David Steele wrote:
>> The 2017-03 commitfest is now in progress. Here's the breakdown:
>>
>> Needs review: 128
>> Waiting on Author: 26
>> Ready for Committer: 26
>> Total: 180
> Not
On Thu, Mar 2, 2017 at 4:42 AM, David Steele wrote:
> The 2017-03 commitfest is now in progress. Here's the breakdown:
>
> Needs review: 128
> Waiting on Author: 26
> Ready for Committer: 26
> Total: 180
Not quite a record haul but close.
--
Thomas Munro
The 2017-03 commitfest is now in progress. Here's the breakdown:
Needs review: 128
Waiting on Author: 26
Ready for Committer: 26
Total: 180
If you are an author and have a patch in the "Waiting for Author" state
please update it as soon as you can. Otherwise, jump in and start
reviewing!
--