aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-10-04 13:41:09 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2012-10-04 13:41:09 -0400
commit6c33084fa2eb1c1cce61def72d8eb7c91a69d525 (patch)
tree13042ffa8843dbe309bee740fe5006f100367803 /src/backend/access/gist/gistvacuum.c
parent412a4295b5390cfe4fd5b9fc84a25c6e2d1aa0ad (diff)
downloadpostgresql-6c33084fa2eb1c1cce61def72d8eb7c91a69d525.tar.gz
postgresql-6c33084fa2eb1c1cce61def72d8eb7c91a69d525.zip
Fix permissions explanations in CREATE DATABASE and CREATE SCHEMA docs.
These reference pages still claimed that you have to be superuser to create a database or schema owned by a different role. That was true before 8.1, but it was changed in commits aa1110624c08298393dfce996f7b21809d98d3fd and f91370cd2faf1fd35a1ac74d84652a85ed841919 to allow assignment of ownership to any role you are a member of. However, at the time we were thinking of that primarily as a change to the ALTER OWNER rules, so the need to touch these two CREATE ref pages got missed.
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions