Re: cannot restore schema with is not distinct from on hstore sincePG 9.6.8
| От | David G. Johnston |
|---|---|
| Тема | Re: cannot restore schema with is not distinct from on hstore sincePG 9.6.8 |
| Дата | |
| Msg-id | CAKFQuwYAY3hV9yE3D9SiaSfM9JJBu9DFOh0y3C6ZKE1s2OSY8w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: cannot restore schema with is not distinct from on hstore since PG 9.6.8 (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: cannot restore schema with is not distinct from on hstore since PG 9.6.8
|
| Список | pgsql-hackers |
So this is all pretty messy, but on the bright side, fixing it would allow
cleaning up some ancient squishy coding in ruleutils.c. It wouldn't be
controversial as just a v12 addition, perhaps ... but do we have a choice
about back-patching? Dump/restore failures are not good.
I think serious consideration needs to be given to ways to allow the user of pg_dump/pg_restore to choose the prior, less secure, mode of operation.
IMO the risk surface presented to support back-patching the behavioral changes was not severe enough to do so in the first place. I'm presuming undoing the back-patch will be shot down without mercy but at least consider an escape hatch for unafflicted secure systems that just happen to depend on search_path more than a super-hardened system would.
David J.
В списке pgsql-hackers по дате отправления: