From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Thomas Alton <thomas(dot)alton(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [BUGS] BUG #14153: Unrecognized node type error when upsert is present in recursive CTE |
Date: | 2016-05-23 23:33:25 |
Message-ID: | CAM3SWZSSF9dSauYyp+Bt2Hu0q31Y1-28x2bO6L05=tNs8zrtRQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Mon, May 23, 2016 at 4:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> You also have to be aware of the new thing, which a lot of hackers
>> will not be, if awareness of COPY_PARSE_PLAN_TREES is anything to go
>> by.
>
> I doubt that anybody ever enables that in manual builds anyway.
> The important thing is to have at least one buildfarm animal using it,
> which there soon will be.
I manually enable it sometimes. And, I've pointed out bugs that that
would have caught to other hackers during review a couple of times.
That's my view. I'm not going to make a fuss about it.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | digoal | 2016-05-24 14:41:46 | BUG #14155: bloom index error with unlogged table |
Previous Message | Tom Lane | 2016-05-23 23:27:53 | Re: Re: [BUGS] BUG #14153: Unrecognized node type error when upsert is present in recursive CTE |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-05-23 23:41:37 | Re: BTREE_BUILD_STATS build is broken |
Previous Message | Tom Lane | 2016-05-23 23:27:53 | Re: Re: [BUGS] BUG #14153: Unrecognized node type error when upsert is present in recursive CTE |