diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2014-11-04 13:24:06 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2014-11-04 13:24:06 -0500 |
| commit | 33f80f8480434f02beb940b8f0627d534f3fd3af (patch) | |
| tree | 732a384307def47e474403494f9df61195a15921 /src/backend/access/gist/gistxlog.c | |
| parent | 5028f22f6eb0579890689655285a4778b4ffc460 (diff) | |
| download | postgresql-33f80f8480434f02beb940b8f0627d534f3fd3af.tar.gz postgresql-33f80f8480434f02beb940b8f0627d534f3fd3af.zip | |
Drop no-longer-needed buffers during ALTER DATABASE SET TABLESPACE.
The previous coding assumed that we could just let buffers for the
database's old tablespace age out of the buffer arena naturally.
The folly of that is exposed by bug #11867 from Marc Munro: the user could
later move the database back to its original tablespace, after which any
still-surviving buffers would match lookups again and appear to contain
valid data. But they'd be missing any changes applied while the database
was in the new tablespace.
This has been broken since ALTER SET TABLESPACE was introduced, so
back-patch to all supported branches.
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions