aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-07-20 16:30:05 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-07-20 16:30:05 +0000
commit6d8afdee000f719c8d63ae383053803935e880d9 (patch)
tree802a4ed69fc70b6f2ee06a1d7d7a697f537b77f3 /src/backend/access/gist/gist.c
parenta0b2bb8ced532daf8ea173d280334109fe87e88a (diff)
downloadpostgresql-6d8afdee000f719c8d63ae383053803935e880d9.tar.gz
postgresql-6d8afdee000f719c8d63ae383053803935e880d9.zip
Fix WAL replay of truncate operations to cope with the possibility that the
truncated relation was deleted later in the WAL sequence. Since replay normally auto-creates a relation upon its first reference by a WAL log entry, failure is seen only if the truncate entry happens to be the first reference after the checkpoint we're restarting from; which is a pretty unusual case but of course not impossible. Fix by making truncate entries auto-create like the other ones do. Per report and test case from Dharmendra Goyal.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions