'but then I don't have accurate statistics on my toasted table..
On Fri, Feb 15, 2019, 3:39 PM Alvaro Herrera On 2019-Feb-14, Mariel Cherkassky wrote:
>
> > I meant the anaylze, if anaylze will run very often on the original
> table,
> > arent there disadvantages for it ?
>
> It'll waste time
Hi Sugathi,
That sounds like a perfect task for a view if the joins are all the same.
~Ben
On Fri, Feb 15, 2019 at 9:36 AM suganthi Sekar
wrote:
> Hi,
>
>
> yes i accept , but when i will do for existing tables, i am facing issue.
>
>
>
> I have created 100 Function , all the function
Hi,
On 2019-02-14 17:27:40 +, Jung, Jinho wrote:
> ### QUERY 2:
>
> select distinct
> ref_0.i_im_id as c0,
> ref_1.ol_dist_info as c1
> from
> public.item as ref_0 right join
> public.order_line as ref_1
> on (ref_0.i_id = 5)
>
> - Commit: 84f9a35 (Improve
Hi Jeff,
Thanks for the feedback! The git bisect idea was particularly helpful.
We use query complexity constraints in sqlfuzz to ensure that the constructed
queries are realistic (e.g., limit the query size, automatically minimize the
query, avoid esoteric expressions and functions,
On 2019-Feb-14, Mariel Cherkassky wrote:
> I meant the anaylze, if anaylze will run very often on the original table,
> arent there disadvantages for it ?
It'll waste time and resources pointlessly. Don't do it -- it won't do
any good.
--
Álvaro Herrera
