| From: | Vick Khera <vivek(at)khera(dot)org> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: DB on mSATA SSD |
| Date: | 2015-04-23 14:31:53 |
| Message-ID: | CALd+dceUQTjfgCvkZWCFPc2MvrGKQV6zvn0T1Sc1bHjw442FOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 23, 2015 at 9:36 AM, Job <Job(at)colliniconsulting(dot)it> wrote:
> We have a table, about 500Mb, that is updated and written every day.
> When machines updates, table is truncated and then re-populated with
> pg_bulk.
> But i think we strongly writes when importing new data tables..
>
so this is static data you update once per day from some external source?
seems like a good candidate to put into RAM if you have enough. make sure
your ram disk is not backed by swap, though.
how and how much do you query it? perhaps you don't even need indexes if
it is on SSD or RAM disk.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2015-04-23 14:34:09 | Re: R: DB on mSATA SSD |
| Previous Message | Andy Colson | 2015-04-23 14:01:14 | Re: What constitutes "reproducible" numbers from pgbench? |