'View'-performance
| От | Alexander Priem |
|---|---|
| Тема | 'View'-performance |
| Дата | |
| Msg-id | 00e801c36259$30b908b0$b696a8c0@APR обсуждение исходный текст |
| Ответ на | Tuning PostgreSQL ("Alexander Priem" <ap@cict.nl>) |
| Ответы |
Re: 'View'-performance
|
| Список | pgsql-performance |
Hi all,
I am wondering about something: I have a table (let's call it "Table") which will contain a lot of records. Every record has a field named "deleted" which can be either NULL or a date value. When this field is NULL, the record in question may be used by a program. If the field contains a date, this field must be considered as "deleted" and cannot be used anymore.
The reason why I don't actually delete such records is that I want to be able to reference them from other locations (for history purposes).
What I am thinking about is creating two views for this table: Table_View and Table_History. Table_View would contain all records where "Deleted is null". Table_History would just contain all records (Select * From Table).
In my program most queries would need to view only the records where deleted is null.
Would " Select * from Table_View Where Name='xxx' " perform worse than " Select * from Table Where deleted is null and Name='xxx' " ?
I ask this because I would like it if I wouldn't have to type "where deleted is null" for about every query in my program. But I will not use this strategy if this would mean serious performance loss...
Thanks in Advance,
Alexander Priem.
В списке pgsql-performance по дате отправления: