Re: Proposal: move column defaults into pg_attribute along with attacl
От | Tom Lane |
---|---|
Тема | Re: Proposal: move column defaults into pg_attribute along with attacl |
Дата | |
Msg-id | 25417.1222172996@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Proposal: move column defaults into pg_attribute along with attacl (Markus Wanner <markus@bluegap.ch>) |
Ответы |
Re: Proposal: move column defaults into pg_attribute along
with attacl
|
Список | pgsql-hackers |
Markus Wanner <markus@bluegap.ch> writes: > Just to understand the issue here: what's the reason for having an OID > for the default value and possible another one for a ACLs, but none for > the attribute itself? Well, as far as the dependency system goes this way is more convenient. If pg_attribute entries had their own OIDs it would be fairly hard to implement DROP TABLE except with an intermediate step of dropping each of the columns one by one, because you'd pretty much have to have explicit pg_depend entries linking each column to its table, and that behavior is what you'd get from the dependency traversal. So that's why we didn't add OIDs (back) to pg_attribute when we invented the dependency system. Default values would need their own OIDs, or at least some distinct representation in pg_depend, in any case. regards, tom lane
В списке pgsql-hackers по дате отправления: