| From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql-server: Dept. |
| Date: | 2004-08-30 03:50:24 |
| Message-ID: | 20040830035024.84F9E5E46C2@svr1.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Dept. of second thoughts: it'd be a good idea to flush buffers
during replay of CREATE DATABASE as well as the first time around.
Else it's possible that the copy operation will copy obsolete blocks.
We are still a long way from guaranteeing anything about using a
recently-written database as a CREATE template, but this seems needed
to ensure the existing behavior holds up during replay.
Modified Files:
--------------
pgsql-server/src/backend/commands:
dbcommands.c (r1.143 -> r1.144)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/commands/dbcommands.c.diff?r1=1.143&r2=1.144)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-08-30 03:52:43 | pgsql-server: Tweak md.c logic to cope with the situation where WAL |
| Previous Message | Bruce Momjian | 2004-08-30 03:31:29 | pgsql-server: Add Win32 service capability to pg_autovacuum. |