Re: [COMMITTERS] pgsql: Fix pg_dump to dump shell types.
От | Peter Eisentraut |
---|---|
Тема | Re: [COMMITTERS] pgsql: Fix pg_dump to dump shell types. |
Дата | |
Msg-id | 55C902E8.2010400@gmx.net обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Fix pg_dump to dump shell types. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [COMMITTERS] pgsql: Fix pg_dump to dump shell types.
|
Список | pgsql-hackers |
On 8/9/15 6:23 PM, Tom Lane wrote: > It looks to me like the reason for this is that pg_dump forces the > "typacl" of a type to be '{=U}' when reading the schema data for a > pre-9.2 type, rather than reading it as NULL (ie default permissions) > which would result in not printing any grant/revoke commands for > the object. > > I do not see a good reason for that; quite aside from this problem, > it means there is one more place that knows the default permissions > for a type than there needs to be. Peter, what was the rationale? This was probably just copied from how proacl and lanacl are handled, which predate typacl by quite a bit. Maybe there was a reason in those days. It might also have something to do with how owner privileges are handled. An explicit '{=U}' doesn't create owner privileges, unlike a null value in that field. Maybe this is necessary if you dump and restore between databases with different user names.
В списке pgsql-hackers по дате отправления: