aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/trigger.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-11-04 13:24:17 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2014-11-04 13:24:17 -0500
commitdb72ad02ece05434bf011725f83d95b10f1505b9 (patch)
treec9b3235e094095e681cf96d949d4901868d79085 /src/backend/commands/trigger.c
parent2c2c1e8ba083a81f8700fa9aac3dfede454e448a (diff)
downloadpostgresql-db72ad02ece05434bf011725f83d95b10f1505b9.tar.gz
postgresql-db72ad02ece05434bf011725f83d95b10f1505b9.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/commands/trigger.c')
0 files changed, 0 insertions, 0 deletions