Re: [sqlsmith] Failed to generate plan on lateral subqueries

From: Andreas Seltenreich <seltenreich(at)gmx(dot)de>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [sqlsmith] Failed to generate plan on lateral subqueries
Date: 2015-12-12 20:30:17
Message-ID: 876103fm06.fsf@elite.ansel.ydns.eu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Stark writes:

> There may be other errors that would be surprising for Tom or Robert. What
> I did with the string argument fuzzer was printed counts for each sqlstate
> for the errors and watched for errors that only occurred occasionally or
> didn't make sense to me.
>
> Also, do you have any timeouts?

I currently set statement_timeout to 1s to avoid wasting time letting
postgres crunch numbers. Less than 0.5% of the queries run into this
timeout.

> Do you have any stats on how long these queries are taking to plan?
> What's the longest query to plan you've found?

No, I'm currently not logging timing spects. The schema I let the
instances log into is part of the repo[1].

> Do you have coverage data for the corpus?

I do have some older numbers for line coverage from before the recent
grammar extension:

| revision | overall | parser |
|----------+---------+--------|
| a4c1989 | 26.0 | 20.4 |

regards,
Andreas

Footnotes:
[1] https://github.com/anse1/sqlsmith/blob/master/log.sql

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2015-12-12 21:14:13 PATCH: track last known XLOG segment in control file
Previous Message Peter Eisentraut 2015-12-12 20:25:24 Re: [COMMITTERS] pgsql: Handle policies during DROP OWNED BY