Re: jaguar is up
| От | Gregory Stark |
|---|---|
| Тема | Re: jaguar is up |
| Дата | |
| Msg-id | 87lk8hki6k.fsf@oxford.xeocode.com обсуждение |
| Ответ на | Re: jaguar is up (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: jaguar is up
|
| Список | pgsql-hackers |
"Tom Lane" <tgl@sss.pgh.pa.us> writes: > I didn't do anything about it at the time, but now I am tempted to > modify LookupOpclassInfo() so that CLOBBER_CACHE_ALWAYS disables > its internal cache. Any objections? That sounds not equivalent to receiving a relcache flush at any particular point in time where a relcache flush could be received. Wouldn't it make more sense (and test more code) to go ahead and cache all the same data but flush it whenever a relcache flush could possibly be received? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services!
В списке pgsql-hackers по дате отправления: