Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"

From: Dimitri <dimitrik(dot)fr(at)gmail(dot)com>
To: "Josh Berkus" <josh(at)agliodbs(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Date: 2007-04-05 19:00:19
Message-ID: 5482c80a0704051200h51fbfb77n8122f1022c0abc66@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Wow, it's excellent! :))

probably the next step is:

ALTER TABLE CACHE ON/OFF;

just to force keeping any table in the cache. What do you think?...

Rgds,
-Dimitri

On 4/5/07, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Dimitri,
>
> > Probably another helpful solution may be to implement:
> >
> > ALTER TABLE LOGGING OFF/ON;
> >
> > just to disable/enable WAL?
>
> Actually, a patch similar to this is currently in the queue for 8.3.
>
> --
> Josh Berkus
> PostgreSQL @ Sun
> San Francisco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message John Allgood 2007-04-05 19:06:14 High Load on Postgres 7.4.16 Server
Previous Message Erik Jones 2007-04-05 18:58:31 Re: a question about Direct I/O and double buffering