From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Thom Brown <thom(at)linux(dot)com>, Rob Wultsch <wultsch(at)gmail(dot)com>, Joshua Berkus <josh(at)agliodbs(dot)com>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: Unlogged vs. In-Memory |
Date: | 2011-05-04 15:51:57 |
Message-ID: | 1304524200-sup-2194@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy 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(at)gmail(dot)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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-05-04 16:21:14 | Re: Unlogged vs. In-Memory |
Previous Message | Simon Riggs | 2011-05-04 15:30:03 | Re: Unlogged vs. In-Memory |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-05-04 15:57:12 | Re: patch for new feature: Buffer Cache Hibernation |
Previous Message | Tom Lane | 2011-05-04 15:44:36 | Re: patch for new feature: Buffer Cache Hibernation |