aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-08-07 16:32:50 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2018-08-07 16:33:08 -0400
commit74c877e8db23df20004f80dd11e383da8cc187a2 (patch)
tree0d0d48913f123b86a7e2050b5a1f36827cf9e6a7 /src/backend/tcop/postgres.c
parent0667d889ea9b9ae298ca899fa53484703bc8fdaf (diff)
downloadpostgresql-74c877e8db23df20004f80dd11e383da8cc187a2.tar.gz
postgresql-74c877e8db23df20004f80dd11e383da8cc187a2.zip
Don't record FDW user mappings as members of extensions.
CreateUserMapping has a recordDependencyOnCurrentExtension call that's been there since extensions were introduced (very possibly my fault). However, there's no support anywhere else for user mappings as members of extensions, nor are they listed as a possible member object type in the documentation. Nor does it really seem like a good idea for user mappings to belong to extensions when roles don't. Hence, remove the bogus call. (As we saw in bug #15310, the lack of any pg_dump support for this case ensures that any such membership record would silently disappear during pg_upgrade. So there's probably no need for us to do anything else about cleaning up after this mistake.) Discussion: https://postgr.es/m/27952.1533667213@sss.pgh.pa.us
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions