This is a fantastic idea. Now how to get it on RDS…
It can be done manually:
https://dba.stackexchange.com/questions/306661/how-to-instal...
PostgreSQL Anonymizer developer here : this was possible with version 0.8 which is now completely unmaintained.
This extension is currently not available on RDS but it is available on many others DBaaS providers : Azure SQL, Google Cloud SQL, Crunchy Bridge, ....
Assuming if it's for a support team or internal users with a lower SLA, I wonder if it's possible to have a small self-hosted PostgreSQL server that basically acts as a shim by holding a foreign-data wrapper connection to the actual RDS instance
In RDS, if you cannot use this, you can create masked view and use query rewrite to make it work.
In my experience PG anonymizer has performance issues when it comes to large queries.
Version 2.0 was released a few days ago. It's a complete rewrite in Rust.
Performance should be better than with v1.x
Same. Lack of RDS support is the only reason we aren’t using this.
PostgreSQL Anonymizer developer here : this was possible with version 0.8 which is now completely unmaintained. This extension is currently not available on RDS but it is available on many others DBaaS providers : Azure SQL, Google Cloud SQL, Crunchy Bridge, ....
Just to jump in here -> We support RDS + more and you can self-host, Neosync.
https://github.com/nucleuscloud/neosync
(I'm one of the co-founders)
I tried to figure out how/if this does what I need and your README had no examples. I clicked a couple of level deep, found no obvious demonstrations and left.
I checked the homepage but I do not watch Loom-style demos personally, definitely not 5 minute ones, and so I left.
-
When I click on OP's link, or just search for it on Google, it takes less than a full page for the extension to show me an extremely straightforward demonstration of its value. You should have something like that.
A simple example of what queries will look like, what setup will look like, all concisely communicated, no 5 minute lectures involved.
+1 for RDS support. I have wanted to use this for a while in our production systems. reply