Seeing this on a 16.1 postgres DB using v16 of this image.
I am not a DBA by any stretch of the imagination so this might be easy to avoid but it appears this is a new security feature in postgres after reading this - https://iifx.dev/en/articles/460205563/understanding-restrict-in-postgresql-dumps-a-new-security-feature
I was attempting to restore a backup using the official postgres image and just placing it in the /docker-entrypoint-initdb.d and letting it restore (on a fresh dir).
I got this error and wondered if there is a way to avoid this without having to manually untar the db, remove the offending sql, then either just place the sql in the dir or perhaps gunzip it back up.
OR is this simply all on the application side and nothing that this image can help with?
Not a huge deal- just curious to see if it can be done away with rather than having manual actions.
Seeing this on a 16.1 postgres DB using v16 of this image.
I am not a DBA by any stretch of the imagination so this might be easy to avoid but it appears this is a new security feature in postgres after reading this - https://iifx.dev/en/articles/460205563/understanding-restrict-in-postgresql-dumps-a-new-security-feature
I was attempting to restore a backup using the official postgres image and just placing it in the /docker-entrypoint-initdb.d and letting it restore (on a fresh dir).
I got this error and wondered if there is a way to avoid this without having to manually untar the db, remove the offending sql, then either just place the sql in the dir or perhaps gunzip it back up.
OR is this simply all on the application side and nothing that this image can help with?
Not a huge deal- just curious to see if it can be done away with rather than having manual actions.