On 2017/07/18 16:20, Etsuro Fujita wrote:
> On 2017/07/18 11:03, Robert Haas wrote:
>> On Mon, Jul 10, 2017 at 5:44 PM, Robert Haas wrote:
>>> The posted patches look OK to me. Barring developments, I will commit
>>> them on 2017-07-17, or send another update by then.
>>
>> Committed them.
>
> T
On 2017/07/18 11:03, Robert Haas wrote:
On Mon, Jul 10, 2017 at 5:44 PM, Robert Haas wrote:
The posted patches look OK to me. Barring developments, I will commit
them on 2017-07-17, or send another update by then.
Committed them.
Thank you!
Best regards,
Etsuro Fujita
--
Sent via pgsql
On Mon, Jul 10, 2017 at 5:44 PM, Robert Haas wrote:
> The posted patches look OK to me. Barring developments, I will commit
> them on 2017-07-17, or send another update by then.
Committed them.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sen
On Sun, Jul 9, 2017 at 3:06 AM, Noah Misch wrote:
> On Fri, Jul 07, 2017 at 06:47:26PM +0900, Amit Langote wrote:
>> On 2017/07/06 16:06, Etsuro Fujita wrote:
>> > Looks odd to me because the error message doesn't show any DETAIL info;
>> > since the CTE query, which produces the message, is the s
On Fri, Jul 07, 2017 at 06:47:26PM +0900, Amit Langote wrote:
> On 2017/07/06 16:06, Etsuro Fujita wrote:
> > Looks odd to me because the error message doesn't show any DETAIL info;
> > since the CTE query, which produces the message, is the same as the above
> > query, the message should also be t