| Title: | Oracle Rdb Wishes and Suggestions |
| Notice: | Please READ note 1.0 before using WRITE or REPLY |
| Moderator: | NOVA::SMITHI |
| Created: | Fri Apr 07 1989 |
| Last Modified: | Mon Jun 02 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 809 |
| Total number of notes: | 4111 |
Row/DVLM caches as I understand it, have a backing store and are
refreshed/able after a crash, in order to return the cache to its
'warm' status.
Any chance on having it that way, even after
- normal closes of database
- truncates (sizing cache shorter, but same width)
- expands (sizing cache taller, but same width)
Similarly, an explicit 'truncate cache {cache}' command to flush
a cache
/los
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 808.1 | HOTRDB::LASTOVICA | Use a fork Luke! | Fri May 30 1997 01:24 | 10 | |
> Similarly, an explicit 'truncate cache {cache}' command to flush
> a cache
Why would one wish to do this?
The other stuff has been talked about and there are some possible
benifits to doing something along these lines (be able to quickly
populate cache). As far as resizing a cache, this might be a bit much
to ask (what rows would you include and what ones would you exclude if
you decided to make the cache smaller?).
| |||||
| 808.2 | NOVA::SANTIAGO | I was a teenage net-random. | Fri May 30 1997 11:34 | 16 | |
truncating a cache might(?) be useful when running different workloads
where the cache doesn't allow row replacement; the user would manually
load it before their job(s)
as far as allowing truncate, an example; you size a cache of 1000r x
500b and note you'll need more rows; so you increase to 2000r; the
older 1000 are reloaded
similarly if you set a cache at 10000r x 500b and you decrease to
5000r, only recover/restore the first 5000 rows; the assuming here is
you lower the height to just above the previous observed usage
if you alter the cache width, then flush it
/los
| |||||