| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andreas Seltenreich <seltenreich(at)gmx(dot)de>, David Fetter <david(at)fetter(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [sqlsmith] Failed to generate plan on lateral subqueries |
| Date: | 2015-12-11 19:25:26 |
| Message-ID: | CAM3SWZT0wqxm=E_+=PHv5mBXyEwTi8san1K+FeuipOLmLx5Ujg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 11, 2015 at 7:58 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I guess that means I have to go back to extending the grammar again :-).
>
> I await the results with interest. Did you note the suggestion about
> trying to stress the ON CONFLICT code with this? You'd need it to
> issue non-SELECT queries, which might create some reproducibility
> issues...
About 80% of the bugs we've seen so far are the type that a tool like
sqlsmith could plausibly catch: bugs that trigger defensive "can't
happen" elog(ERROR, ... ) calls within the planner and rewriter. While
I've been vigilant, I certainly wouldn't be surprised if more were
found, given the total flexibility of the ON CONFLICT syntax.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-12-11 19:43:17 | Re: Bootstrap DATA is a pita |
| Previous Message | Caleb Welton | 2015-12-11 19:15:56 | Re: Bootstrap DATA is a pita |