Re: feature freeze and beta schedule - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: feature freeze and beta schedule
Date
Msg-id CANP8+jLjNTMCe2OvbcPXfMzeNbD43wXGC5qTb=3vFregJtBZoA@mail.gmail.com
Whole thread Raw
In response to Re: feature freeze and beta schedule  (Andres Freund <andres@anarazel.de>)
Responses Re: feature freeze and beta schedule
Re: feature freeze and beta schedule
List pgsql-hackers
On 1 May 2015 at 12:37, Andres Freund <andres@anarazel.de> wrote:
 
* fastbloat
  Not too big, I think it should be easy to commit this.
  => Keep in 'ready for committer'

Will commit soon
 
* Turning off HOT for larger SQL queries
  Seems to have degenerated into a discussion of not really related
  things. I personally would vote for committing something close to what
  Simon proposed last *directly at the beginning* of the next cycle.
  => Move?

Yes, move
 
* Allow "snapshot too old" error, to prevent bloat
  http://archives.postgresql.org/message-id/1361166406.1897609.1424371443904.JavaMail.yahoo%40mail.yahoo.com
  talked about a new version that afaics never materialized
  => Returned with feedback

Would like to review this
  
* Sequence Access Method
  There's been some back and forth between Petr and Heikki on this
  lately.
  => Maybe there's still a chance for 9.5?

Hope so
 
* Sending WAL receiver feedback regularly even if the receiver is under
  heavy load
  Imo more of a bugfix than a feature. I.e. doesn't really concern the
  CF scheduling.

Agreed, bug fix. Will do if Fujii doesn't
 
* Auditing extension
  I'm unclear on the status here. Abhijit said he'll have a look.

Maybe me, but running out of time
   
* TABLESAMPLE clause
  Doesn't seem very far from being done. Some questions about including
  (or not) DDL and contrib modules seem to remain.

Will commit this soon

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_dump: CREATE TABLE + CREATE RULE vs. relreplident
Next
From: Qingqing Zhou
Date:
Subject: Re: Use outerPlanState() consistently in executor code