Recently I submitted a patch for review that allows a non-superuser to practically use a backup taken from pg_dump.
Currently it is a kludge (and well known at that - Ref 1 / Ref 2 / Ref 3 / Ref 4) but since it's (the ideal solution) too big a byte to chew and not in high-demand, it has seen little to no traction in the past decade.
This patch should allow the above. But more importantly, it should also allow regular users of AWS RDS Postgres as well as Google Cloud Postgres databases (who do not get SuperUser access by-design) to reliably use the backups, instead of tinkering with the backup SQLs and remove things like COMMENT ON EXTENSION for it to even run during restoration.
The bad news is that since Postgres 10 has already branched off, I doubt this would see the light of the day (if at all) any time before Postgres 11 (unless there is consensus that it's helpful enough and gets 'back-patched' to Postgres 10 to be released around September 2017).
Update (3rd Oct 2017):
This is now a part of my PsqlForks branch. You can check the related commit here.
Update (26th Jan 2018):
This is now part of the official Postgres v11 branch. You can check the related commit here.
Some Ramblings around Postgres, Tech and everything else in between... a.k.a. robins.in
Showing posts with label pg_dump. Show all posts
Showing posts with label pg_dump. Show all posts
Subscribe to:
Comments (Atom)
3x Faster TID Range Scans - Postgres 19
If you've ever had to scrub significantly large tables—whether updating older records or deleting expired ones—you know the pain of tryi...
-
(Please scroll down to the read the entire-post to know more) Documents required for Christian Marriage Registration (a.k.a. Documents...
-
A recent commit to the PostgreSQL master branch brings a nice quality-of-life optimization for a very common SQL pattern - improving perform...
-
I am just starting my AI journey, and trying to get Ollama to work on my linux box, was an interesting non-AI experience. I noticed, that ev...