aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-01-18 20:44:53 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-01-18 20:44:53 +0000
commitff8f86e7a106ac193d3d4485f47f274163045c66 (patch)
tree8553ed2598300e79f142550d339705cf7d16e00b /src/backend/access/gist/gist.c
parent3dc19e440b0ca854125317d899e34ce0e7a6d416 (diff)
downloadpostgresql-ff8f86e7a106ac193d3d4485f47f274163045c66.tar.gz
postgresql-ff8f86e7a106ac193d3d4485f47f274163045c66.zip
Fix a pg_dump output ordering problem introduced in 8.3 by the addition of
array types for composite types. Although pg_dump understood it wasn't supposed to dump these array types as separate objects, it must include them in the dependency ordering analysis, and it was improperly assigning them the same relatively-high sort priority as regular types. This resulted in effectively moving composite types and tables up to that same high priority, which broke any ordering requirements that weren't explicitly enforced by dependencies. In particular user-defined operator classes, which should come out before tables, failed to do so. Per report from Brendan Jurd. In passing, also fix an ill-considered decision to give text search objects the same sort priority as functions and operators --- the sort result looks a lot nicer if different object types are kept separate. The recent foreign-data patch had copied that decision, making the sort ordering even messier :-(
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions