| From: | Sand Stone <sand(dot)m(dot)stone(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Fwd: persistent read cache |
| Date: | 2018-02-12 01:14:38 |
| Message-ID: | CADrk5qNZQGwJyjJLxKERE3it=8N9i712XVsK68UzVBPcKbi05Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Posted to the wrong alias. Just wonder if anyone else feels such a use
case. Thanks.
---------- Forwarded message ----------
From: Sand Stone <sand(dot)m(dot)stone(at)gmail(dot)com>
Date: Sun, Feb 11, 2018 at 11:34 AM
Subject: persistent read cache
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Hi. I wonder if there is such a thing or extension in the PG world.
Here is my use case. I am using PG (PG10 to be more specific) in a
cloud VM environment. The tables are stored in RAID0 managed SSD
backed attached storage. Depending on the VM I am using, I usually
have 256GB local SSD unused.
I wonder if PG could leverage this local SSD as a read (page/block)
cache, to complement/extend the DRAM by used by shared_buffer today.
Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Durumdara | 2018-02-12 08:31:48 | Remove default privilege from DB |
| Previous Message | Tom Lane | 2018-02-11 23:27:12 | Re: New Copy Formats - avro/orc/parquet |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-02-12 01:35:24 | OCD questions about LWTRANCHE_REPLICATION_ORIGIN |
| Previous Message | Thomas Munro | 2018-02-11 23:52:32 | Removing shm_mq.c's volatile qualifiers |