'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 and
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 having
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 e
> "Jung" == Jung, Jinho writes:
Jung> select distinct
Jung> ref_0.i_im_id as c0,
Jung> ref_1.ol_dist_info as c1
Jung> from
Jung> public.item as ref_0 right join
Jung> public.order_line as ref_1
Jung> on (ref_0.i_id = 5)
Jung> - Commit: 84f9a35 (Improve e
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, restrict
Hi,
yes i accept , but when i will do for existing tables, i am facing issue.
I have created 100 Function , all the function having five table join(now all
partition by date) , now its not possible to change where condition in all 100
Function.
so that i am trying any other possibilities
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 Herrerahttps://www.2ndQuadrant.
Mariel Cherkassky wrote:
> Lets focus for example on one of the outputs :
> postgresql-Fri.log:2019-02-08 05:05:53 EST 24776 LOG: automatic vacuum of
> table "myDB.pg_toast.pg_toast_1958391": index scans: 8
> postgresql-Fri.log- pages: 2253 removed, 13737828 remain
> postgresql-Fri.log- tup
