From: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
---|---|
To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | storage in mem |
Date: | 2021-04-01 15:32:30 |
Message-ID: | CADX_1aYLDx8er4Fo8_MVC2QK+eWvGk--eGq+moKJcCQimLOngQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
too my understanding, postgres is now architected so that engine and
storage are ""splited""
and so one may think that storage code different that the
traditional postgres thing is possible.
I have heard of oracle like redo log things, ..etc
I wonder if a memory thing is on the way, somewhere ?
The why (1) of this question:
its quite easy, nowadays to find blades with 2 TB of RAM. (or even much
more !)
and, to my understanding (correct me if I am wrong !) postgres shared
buffers are not really efficient with "some" Terabyte of allocated space.
The why (2) I may have to do a POC with Sap HANA on one side and postgres
on the other
on machines with a lot of RAM.
so...
can someone shade some light ?
thanks,
Marc MILLAS
Senior Architect
+33607850334
www.mokadb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Brian Dunavant | 2021-04-01 15:49:40 | Re: Is replacing transactions with CTE a good idea? |
Previous Message | Glen Huang | 2021-04-01 15:29:57 | Re: Is replacing transactions with CTE a good idea? |