| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Thomas Lockhart" <lockhart(at)fourpalms(dot)org> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Syscaches should store negative entries, too |
| Date: | 2002-01-30 10:25:31 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA42128EB@m0114.s-mxs.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> However, what you probably wouldn't want to do is cache negative lookups
> that don't end up producing results or are not part of a search chain at
> all. Those are user errors and not likely to be repeated and do not need
> to be optimized.
But this also is resolved by the LRU mechanism, no ?
People are not going to issue the same errors repeatedly,
but if they do, we are still interested in minimizing the
resource consumption.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trond Eivind Glomsrød | 2002-01-30 13:35:50 | Re: inline is not ANSI C |
| Previous Message | Zeugswetter Andreas SB SD | 2002-01-30 10:21:42 | Re: Improving backend launch time by preloading relcache |