aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-07-20 16:29:59 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-07-20 16:29:59 +0000
commit85506ffbd51e15dffbd307e4d1060cfffb24c9e0 (patch)
tree5a543ec996874f02f61662d251e241aa1092a864 /src/backend/access/gist/gistscan.c
parent8208fb4b6305bfdd9b89faa6b70fc58b59338d53 (diff)
downloadpostgresql-85506ffbd51e15dffbd307e4d1060cfffb24c9e0.tar.gz
postgresql-85506ffbd51e15dffbd307e4d1060cfffb24c9e0.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/gistscan.c')
0 files changed, 0 insertions, 0 deletions