| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Ana Cerejo" <ana(dot)cerejo(at)yale(dot)edu> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pre-loading a user table. |
| Date: | 2004-04-02 08:20:56 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA40184D051@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Why do you think it useful to preload something during InitPostgres,
> anyway? Any heavily used table will certainly be present in shared
> buffers already, and even more surely present in kernel buffers.
And if you really want it preloaded you can issue dummy selects
with a client right after startup. I really think locking a table into
memory is a worthless feature if a good buffer manager is at work.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2004-04-02 08:22:41 | Re: Inconsistent behavior on Array & Is Null? |
| Previous Message | Tom Lane | 2004-04-02 07:53:38 | Re: Inconsistent behavior on Array & Is Null? |