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.
dbcommands.c (r1.146 -> r1.147)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2004-11-18 01:19:45|
|Subject: pgsql: Back-patch fix for ALTER DATABASE failing to flush pg_database |
|Previous:||From: Michael Fuhr||Date: 2004-11-18 00:49:06|
|Subject: Re: pgsql: Remove ill-considered suppression of gcc warnings in plperl, and|