Re: [HACKERS] CTE inlining - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] CTE inlining
Date
Msg-id 20bbf396-eeea-f82c-ed5f-7dbcbbc5b76f@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] CTE inlining  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: [HACKERS] CTE inlining  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On 5/5/17 08:43, David Rowley wrote:
> How about we get the ball rolling on this in v10 and pull that part
> out of the docs. If anything that'll buy us a bit more wiggle room to
> change this in v11.
> 
> I've attached a proposed patch.

If we just tell them that the thing they might have relied on might go
away, without a replacement to suggest, then we're just confusing and
scaring them, no?

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



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] proposal psql \gdesc
Next
From: David Fetter
Date:
Subject: Re: [HACKERS] idea: custom log_line_prefix components besidesapplication_name