From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Thom Brown <thom(at)linux(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Rob Wultsch <wultsch(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [pgsql-advocacy] Unlogged vs. In-Memory |
Date: | 2011-09-24 19:24:49 |
Message-ID: | m2hb41vj3y.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Basically, for every unlogged table, you get an empty _init fork, and
> for every index of an unlogged table, you get an _init fork
> initialized to an empty index. The _init forks are copied over the
> main forks by the startup process before entering normal running.
Let's call that metadata.
> Well, we could certainly Decree From On High that the _init forks are
> all going to be stored under $PGDATA rather than in the tablespace
> directories. That would make things simple. Of course, it also means
And now you need to associate a non volatile tablespace where to store
the metadata of your volatile tablespace where you want to store
unlogged data. And we already have a default tablespace, of course.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua Berkus | 2011-09-25 18:38:45 | Time to dust off your Ingres migration skills |
Previous Message | Brendan Jurd | 2011-09-24 04:19:59 | Re: Wikipedia's Isolation page |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua Berkus | 2011-09-24 19:49:47 | Re: unite recovery.conf and postgresql.conf |
Previous Message | Robert Haas | 2011-09-24 19:23:12 | Re: [PATCH] Log crashed backend's query (activity string) |