Re: To use a VIEW or not to use a View.....
| От | Tomasz Myrta |
|---|---|
| Тема | Re: To use a VIEW or not to use a View..... |
| Дата | |
| Msg-id | 3E2EC4E9.7000809@klaster.net обсуждение исходный текст |
| Ответ на | To use a VIEW or not to use a View..... ("Ries van Twisk" <ries@jongert.nl>) |
| Ответы |
Re: To use a VIEW or not to use a View.....
|
| Список | pgsql-sql |
Jan Wieck wrote:
>Use tables, views and views over views, it's all fine and your indexes
>will be used.
I can't agree with using views over views. It has some limitations.
I asked about it on this list several months ago
and Tom Lane's conclusion was:
>> Tomasz Myrta <jasiek@klaster.net> writes:
>> I'd like to split queries into views, but I can't join them - planner
>> search all of records instead of using index. It works very slow.
I think this is the same issue that Stephan identified in his response
to your other posting ("sub-select with aggregate"). When you writeFROM x join y using (col) WHERE x.col = const
the WHERE-restriction is only applied to x. I'm afraid you'll need
to writeFROM x join y using (col) WHERE x.col = const AND y.col = const
Ideally you should be able to write justFROM x join y using (col) WHERE col = const
but I think that will be taken the same as "x.col = const" :-(
regards, tom lane
I don't know if anything changed on 7.3.
Regards,
Tomasz Myrta
В списке pgsql-sql по дате отправления: