Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000" - Mailing list pgsql-performance

From Dimitri
Subject Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Date
Msg-id 5482c80a0704051200h51fbfb77n8122f1022c0abc66@mail.gmail.com
Whole thread Raw
In response to Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"  (Josh Berkus <josh@agliodbs.com>)
List 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@agliodbs.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
>

pgsql-performance by date:

Previous
From: Erik Jones
Date:
Subject: Re: a question about Direct I/O and double buffering
Next
From: "John Allgood"
Date:
Subject: High Load on Postgres 7.4.16 Server