| From: | Glenn <spamproof(at)pluggedin(dot)bc(dot)ca> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | How to cache database? |
| Date: | 2001-04-08 05:11:36 |
| Message-ID: | 3ACFF308.6A7FD6B5@pluggedin.bc.ca |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Reading discussions on scalability, I saw Tom Lane reccomend caching a
"large chunk" of a database as a path to faster performance. Is there
any place I can read up (rtfm) on how to do this? (Specifically
redhat6.2 system running postgres 6.5.x soon to be postgres 7.x)
I expect this could really speed up my database access as I'm dealing
with a small database that has many small nearly static tables (the
restaurant menus) and a few larger highly active tables (customer data
and order data). The small tables are <100 rows each while the large
are thousands and tens of thousands in size. The database is small
(currently dumps into ~6megs) and should be able live in ram without
difficulty.
--
Glenn Wittrock
Linux: when you need to run like a greased weasel.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Doug McNaught | 2001-04-08 05:17:24 | Re: Why are quotes required around table / column names in SQL statements? |
| Previous Message | Alastair D'Silva | 2001-04-08 05:04:16 | Inheritance and referential integritry in 7.0.3 |