From: | Vinicius Segalin <vinisegalin(at)gmail(dot)com> |
---|---|
To: | Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
Cc: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Query generator |
Date: | 2016-10-16 22:30:03 |
Message-ID: | CAAeH1nDP1f83e5PiQAUQ4_4RyFFDVV1un+j5Q=QLLZ5AjUzmDg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2016-10-16 8:54 GMT-02:00 Andreas Seltenreich <seltenreich(at)gmx(dot)de>:
> Vinicius Segalin <vinisegalin(at)gmail(dot)com> writes:
>
> > 2016-09-29 16:32 GMT-03:00 Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>:
> >
> > > You should try sqlsmith (https://github.com/anse1/sqlsmith) which
> works
> > > very well.
> >
> > I had found this one before, but all I could get was queries using
> > "standard" tables, like the ones from pg_catalog and
> > information_schema. It didn't generate queries from the tables I've
> > created. Was I doing something wrong?
>
> It should pick your relations with the same likelihood it picks the
> catalog tables. You could verify this for with, e.g.,
>
> sqlsmith --dry-run | grep your_table_name
>
> Thanks to Julien, sqlsmith's master branch now has an option
> --exclude-catalog that inhibits use of catalog relations. If you are
> building from github, you might want to give it another chance with this
> option. I'll probably do a proper release in next two weeks.
>
> Feedback welcome :-)
>
> regards,
> Andreas
>
Yes, I was talking in private with him and he came up with this solution.
Thank you again, Julien.
I need to try it again, did a quick test on friday, but it looks like it
works perfectly! :)
From | Date | Subject | |
---|---|---|---|
Next Message | Bastien Bodart | 2016-10-17 15:04:55 | truncate table restart identity for non-owner |
Previous Message | Christoph Berg | 2016-10-16 15:42:42 | Re: could not connect to server |