Re: unlogged tables
Alvaro Herrera <alvherre@commandprompt.com>
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers <pgsql-hackers@postgresql.org>, Andrew Dunstan <andrew@dunslane.net>, Kenneth Marshall <ktm@rice.edu>, Tom Lane <tgl@sss.pgh.pa.us>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, marcin mank <marcin.mank@gmail.com>, Andy Colson <andy@squeakycode.net>
Date: 2010-11-17T21:06:23Z
Lists: pgsql-hackers
Excerpts from Robert Haas's message of mié nov 17 17:51:37 -0300 2010: > On Wed, Nov 17, 2010 at 3:35 PM, Andres Freund <andres@anarazel.de> wrote: > > How can you get a buffer which was no written out *at all*? Do you want to > > force all such pages to stay in shared_buffers? That sounds quite a bit more > > complicated than what you proposed... > > Oh, you're right. We always have to write buffers before kicking them > out of shared_buffers, but if we don't fsync them we have no guarantee > they're actually on disk. You could just open all the segments and fsync them. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support