Re: Unlogged vs. In-Memory

Alvaro Herrera <alvherre@commandprompt.com>

From: Alvaro Herrera <alvherre@commandprompt.com>

To: Simon Riggs <simon@2ndquadrant.com>

Cc: Robert Haas <robertmhaas@gmail.com>, Magnus Hagander <magnus@hagander.net>, Thom Brown <thom@linux.com>, Rob Wultsch <wultsch@gmail.com>, Joshua Berkus <josh@agliodbs.com>, PostgreSQL Advocacy <pgsql-advocacy@postgresql.org>

Date: 2011-05-04T15:51:57Z

Lists: pgsql-hackers

Excerpts from Simon Riggs's message of mié may 04 12:30:03 -0300 2011:
> On Wed, May 4, 2011 at 3:02 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> 
> > To make PG do it automatically, we'd need to store the _init forks in
> > a different tablespace from the remaining forks.  That's probably
> > possible, but it seems complicated.
> 
> Sounds much better way actually and also quite easy. All we do is keep
> the init forks in a subdirectory that identifies the tablespace they
> relate to.

Is there a way to "update" the init fork after table creation?  If so,
you could periodically copy stuff from the current contents (main fork)
into the init fork; or update the init fork with some command (think
UPDATE or COPY).

(Why is this in -advocacy?)

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support