On 7/2/07, Tom Lane <[EMAIL PROTECTED]> wrote:
David Fetter <[EMAIL PROTECTED]> writes:
> On Sun, Jul 01, 2007 at 03:55:11PM -0400, Alvaro Herrera wrote:
>> So mount a ramdisk and initdb in there.
> You could also put a tablespace on a ramdisk and create the table
> there.
Thanks for this hint
On 7/1/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
So mount a ramdisk and initdb in there.
As I wrote in my first post that is the straight forward approach.
The question was is there something else that exists in PostgreSQL and
will do the same job.
---(end of broadc
On 7/1/07, Tom Lane <[EMAIL PROTECTED]> wrote:
That's why I asked if you thought losing data at crash was a feature
Yes it is. I don't want to actually save the data on disk.
---(end of broadcast)---
TIP 6: explain analyze is your friend
On 7/1/07, Tom Lane <[EMAIL PROTECTED]> wrote:
As long as shared_buffers is high enough, there doesn't seem to be much
point in worrying about this; the incremental performance gain will be
minimal since everything will be in RAM anyway.
Yes it will be but this does not mean there will be no di
Hello,
is there anything to emulate the MySQL memory table engine?
A straight forward solution is to create a ramfs volume and mount/link
content under /var/lib/postresql there. Then add some scripts to
save/restore databases when the server restarts.
I am wondering is there something else?
Greet
