Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: PostgreSQL as a local in-memory cache
- From: Robert Haas <robertmhaas(at)gmail(dot)com>
- To: Josh Berkus <josh(at)agliodbs(dot)com>
- Cc: postgres performance list <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: PostgreSQL as a local in-memory cache
- Date: Mon, 21 Jun 2010 18:14:39 -0400
- Message-id: <AANLkTinyzvzA3mGTQEM1eYY0K818qi0M_q19aY_pDViq@mail.gmail.com> <text/plain>
On Thu, Jun 17, 2010 at 1:29 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote: > a) Eliminate WAL logging entirely In addition to global temporary tables, I am also planning to implement unlogged tables, which are, precisely, tables for which no WAL is written. On restart, any such tables will be truncated. That should give you the ability to do this (by making all your tables unlogged). -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
- References:
- PostgreSQL as a local in-memory cache
- From: jgardner(at)jonathangardner(dot)net
- Re: PostgreSQL as a local in-memory cache
- From: jgardner(at)jonathangardner(dot)net
- Re: PostgreSQL as a local in-memory cache
- From: Josh Berkus
- PostgreSQL as a local in-memory cache
- Prev by Date: Re: Low perfomance SUM and Group by large databse
- Next by Date: raid10 write performance
- Previous by thread: Re: PostgreSQL as a local in-memory cache
- Next by thread: Re: PostgreSQL as a local in-memory cache
- Indexes: