| From: | "David Blood" <david(at)matraex(dot)com> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Pinning a table into memory |
| Date: | 2002-10-04 16:46:57 |
| Message-ID: | 03a301c26bc5$a799a970$1f00a8c0@redwood |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-performance pgsql-sql |
In Oracle you can Pin large objects into memory to prevent frequent
reloads. Is there anyway to do this with Postgres? It appears that some
of our tables that get hit a lot may get kicked out of memory when we
access some of our huge tables. Then they have to wait for I/O to get
loaded back in.
David Blood
Matraex, Inc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-10-04 17:30:21 | Re: transactions |
| Previous Message | Tom Lane | 2002-10-04 16:44:48 | Re: pg_restore issue.. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-10-04 16:53:11 | Re: Return of INSTEAD rules |
| Previous Message | Michael Paesold | 2002-10-04 16:44:04 | Re: [SQL] [GENERAL] CURRENT_TIMESTAMP |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2002-10-04 18:13:09 | Re: Comparitive UPDATE speed |
| Previous Message | Andrew Sullivan | 2002-10-04 16:44:03 | Re: Comparitive UPDATE speed |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-10-04 18:47:47 | Re: Pinning a table into memory |
| Previous Message | Michael Paesold | 2002-10-04 16:38:21 | Re: Large databases, performance |