-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension Request: Postgresql Anonymizer #3796
Comments
@lubennikovaav to enable it this week |
Duplicate: #4970 |
PR in pg_anonymizer neondatabase/postgresql_anonymizer#3 To test in on preview today/tomorrow |
Status update: will be picked up after pgbouncer fixes |
in testing |
in review |
This extension is now available on staging and prod behind feature flag @raoufchebri is testing it now, |
@seymourisdead, I guess it can be a good candidate for feature preview that users can enable on their behalf |
It's on production under feature flag |
Figure out workflow for users. No issues found during testing. @raoufchebri Do you have an update on the rollout? |
According to Raouf the extension is tested, and works well. There are some inherent challenges, these are listed and explained in an upcoming blog posting. |
Rollout plan:
|
There is a feature flag, which is not enabled for all users. Enable it for everyone. Then remove the feature flag. |
See if the error message can be improved, and point the user to what needs to be done (loading the library). |
https://www.postgresql.org/about/news/postgresql-anonymizer-10-privacy-by-design-for-postgres-2452/
The text was updated successfully, but these errors were encountered: