From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mladen Gogala <gogala(dot)mladen(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Lazy View's Column Computing |
Date: | 2021-08-02 23:38:49 |
Message-ID: | 1661401.1627947529@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Mladen Gogala <gogala(dot)mladen(at)gmail(dot)com> writes:
> The query from the view would probably merge view with the original and
> optimize everything as a single query. Unfortunately, there is no way to
> tell:
> mgogala=# explain select ename,job,sal from acct_view;
> QUERY PLAN
> ----------------------------------------------------
> Seq Scan on emp (cost=0.00..1.18 rows=3 width=21)
> Filter: (deptno = 10)
> (2 rows)
> The only tool that you have at your disposal is EXPLAIN.
No ... EXPLAIN VERBOSE would fill in the detail you want,
as somebody else already demonstrated in this thread.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gilar Ginanjar | 2021-08-03 01:42:09 | Unexpected block ID found when reading data |
Previous Message | Mladen Gogala | 2021-08-02 23:27:02 | Re: Lazy View's Column Computing |