chore: update meta for 5.2. update docs

META.json

@@ -1,7 +1,7 @@
 {
     "name": "pg_partman",
     "abstract": "Extension to manage partitioned tables by time or ID",
-    "version": "5.1.0",
+    "version": "5.2.0",
     "maintainer": [
         "Keith Fiske <[email protected]>"
     ],
@@ -20,9 +20,9 @@
     },
     "provides": {
         "pg_partman": {
-            "file": "sql/pg_partman--5.1.0.sql",
+            "file": "sql/pg_partman--5.2.0.sql",
             "docfile": "doc/pg_partman.md",
-            "version": "5.1.0",
+            "version": "5.2.0",
             "abstract": "Extension to manage partitioned tables by time or ID"
         }
     },

README.md

@@ -72,7 +72,7 @@ CREATE SCHEMA partman;
 CREATE EXTENSION pg_partman SCHEMA partman;
 ```
 
-pg_partman does not require a superuser to run, but currently still requires it to be installed. If not using a superuser, it is recommended that a dedicated role is created for running pg_partman functions and to be the owner of all partition sets that pg_partman maintains. At a minimum this role will need the following privileges (assuming pg_partman is installed to the `partman` schema and that dedicated role is called `partman_user`):
+pg_partman does not require a superuser to run nor to be installed (see [Extension Files](https://www.postgresql.org/docs/current/extend-extensions.html#EXTEND-EXTENSIONS-FILES) section of upstream docs) . If not using a superuser, it is recommended that a dedicated role is created for running pg_partman functions and to be the owner of all partition sets that pg_partman maintains. At a minimum this role will need the following privileges (assuming pg_partman is installed to the `partman` schema and that dedicated role is called `partman_user`):
 
 ```sql
 CREATE ROLE partman_user WITH LOGIN;

test/README_test.md

@@ -9,7 +9,7 @@ A minimum version of pgtap 1.2.0 is required for pg_partman's test suite.
 
 ***WARNING: You MUST increase max_locks_per_transaction above the default value of 64. A value of 128 has worked well so far with existing tests. This is due to the subpartitioning tests that create/destroy several hundred tables in a single transaction. If you don't do this, you risk a cluster crash when running subpartitioning tests.***
 
-Tests assume that the required extensions have been installed in the following schemas:
+Tests assume that the required extensions have been installed in the following schemas (unless otherwise noted in that specific test):
 
     pg_partman: partman
     pgTAP: public
@@ -22,7 +22,7 @@ If you've installed any of the above extensions in a different schema and would
 
 Once that's done, it's best to use the **pg_prove** script that pgTAP comes with to run all the tests. If you don't have pg_prove available from your installation source, it is typically available via a perl library package (Ex. `libtap-parser-sourcehandler-pgtap-perl` on Ubuntu).
 
-I like using the  -o, -v -f options to get more useful feedback.
+I like using the  -o -v -f options to get more useful feedback.
 
 ```sql
     pg_prove -ovf /path/to/partman/test/*.sql