aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuildbuffers.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-02-10 22:38:15 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2015-02-10 22:38:15 -0500
commit9feefedf9e92066fa6609d1e1e17b4892d81716f (patch)
treee9fb5f90192bb56b32d20596f4d4cdc389b5acc3 /src/backend/access/gist/gistbuildbuffers.c
parent1a179f36f7c612d3560a72396c559cd876dfab6b (diff)
downloadpostgresql-9feefedf9e92066fa6609d1e1e17b4892d81716f.tar.gz
postgresql-9feefedf9e92066fa6609d1e1e17b4892d81716f.zip
Fix pg_dump's heuristic for deciding which casts to dump.
Back in 2003 we had a discussion about how to decide which casts to dump. At the time pg_dump really only considered an object's containing schema to decide what to dump (ie, dump whatever's not in pg_catalog), and so we chose a complicated idea involving whether the underlying types were to be dumped (cf commit a6790ce85752b67ad994f55fdf1a450262ccc32e). But users are allowed to create casts between built-in types, and we failed to dump such casts. Let's get rid of that heuristic, which has accreted even more ugliness since then, in favor of just looking at the cast's OID to decide if it's a built-in cast or not. In passing, also fix some really ancient code that supposed that it had to manufacture a dependency for the cast on its cast function; that's only true when dumping from a pre-7.3 server. This just resulted in some wasted cycles and duplicate dependency-list entries with newer servers, but we might as well improve it. Per gripes from a number of people, most recently Greg Sabino Mullane. Back-patch to all supported branches.
Diffstat (limited to 'src/backend/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions