Skip site navigation (1) Skip section navigation (2)

pgsql: Force pg_database updates out to disk immediately after ALTER

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Force pg_database updates out to disk immediately after ALTER
Date: 2004-11-18 01:14:27
Message-ID: 20041118011427.BA5C53A44D8@svr1.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Force pg_database updates out to disk immediately after ALTER DATABASE;
this is to avoid scenarios where incoming backends find no live copies
of a database's row because the only live copy is in an as-yet-unwritten
shared buffer, which they can't see.  Also, use FlushRelationBuffers()
for forcing out pg_database, instead of the much more expensive BufferSync().
There's no need to write out pages belonging to other relations.

Modified Files:
--------------
    pgsql/src/backend/commands:
        dbcommands.c (r1.146 -> r1.147)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c.diff?r1=1.146&r2=1.147)

pgsql-committers by date

Next:From: Tom LaneDate: 2004-11-18 01:19:45
Subject: pgsql: Back-patch fix for ALTER DATABASE failing to flush pg_database
Previous:From: Michael FuhrDate: 2004-11-18 00:49:06
Subject: Re: pgsql: Remove ill-considered suppression of gcc warnings in plperl, and

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group