From: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
---|---|
To: | Albretch <lbrtchx(at)hotmail(dot)com> |
Subject: | Re: CREATE DATABASE on the heap with PostgreSQL? |
Date: | 2004-06-06 18:43:44 |
Message-ID: | 40C365E0.6090905@bigfoot.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Albretch wrote:
> After RTFM and googling for this piece of info, I think PostgreSQL
> has no such a feature.
>
> Why not?
>
> . Isn't RAM cheap enough nowadays? RAM is indeed so cheap that you
> could design diskless combinations of OS + firewall + web servers
> entirely running off RAM. Anything needing persistence you will send
> to the backend DB then
> . Granted, coding a small Data Structure with the exact functionality
> you need will do exactly this "keeping the table's data on the heap".
> But why doing this if this is what DBMS have been designed for in the
> first place? And also, each custom coded DB functionality will have to
> be maintaned.
>
> Is there any way or at least elegant hack to do this?
>
> I don't see a technically convincing explanation to what could be a
> design decision, could you explain to me the rationale behind it, if
> any?
If you access a table more frequently then other and you have enough
RAM your OS will mantain that table on RAM, don't you think ?
BTW if you trust on your UPS I'm sure you are able to create a RAM
disk and place that table in RAM.
Regards
Gaetano Mendola
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2004-06-06 19:30:48 | Re: table content transfer from mysql to postgresql |
Previous Message | Jeff Davis | 2004-06-06 18:33:51 | Re: [HACKERS] Slony-I goes BETA (possible bug) |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-06 21:33:59 | Re: Case preserving - suggestions |
Previous Message | Jeff Davis | 2004-06-06 18:33:51 | Re: [HACKERS] Slony-I goes BETA (possible bug) |