Force pg_database updates out to disk immediately after ALTER DATABASE;
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 18 Nov 2004 01:14:26 +0000 (01:14 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 18 Nov 2004 01:14:26 +0000 (01:14 +0000)
commitb2a2f4cef7e180735ab9e80cea3a0f73cd4edc58
tree944889e1fafc6098783581443388c4de59a9b23d
parentc36496a1011e1b66947173dba4eefdec2a95669b
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.
src/backend/commands/dbcommands.c