Re: Any reason why the default_with_oids GUC is still there?
От | Tom Lane |
---|---|
Тема | Re: Any reason why the default_with_oids GUC is still there? |
Дата | |
Msg-id | 10387.1285106740@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Any reason why the default_with_oids GUC is still there? (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Any reason why the default_with_oids GUC is still there?
Re: Any reason why the default_with_oids GUC is still there? Re: Any reason why the default_with_oids GUC is stillthere? |
Список | pgsql-hackers |
Josh Berkus <josh@agliodbs.com> writes: > On 9/20/10 10:59 PM, Heikki Linnakangas wrote: >> Backwards-compatibility? ;-) There hasn't been any pressing reason to >> remove it. > Any application which needed it (like OpenACS) just got broken when we > removed add_missing_from. Let alone the typecasting changes in 8.3. Huh? There's no reason to assume that those features are connected. > Personally, I find removing GUCS to be a worthwhile goal in itself. We > have well over 200 now. Usually we don't remove GUCs (or other backwards-compatibility features) until there's some positive reason to do so. I don't see one at the moment for default_with_oids. Reducing the length of the GUC list by 0.5% doesn't seem like an adequate reason for possibly breaking old apps. Mind you, it wouldn't take a *big* reason to persuade me to remove it. But bigger than that. regards, tom lane
В списке pgsql-hackers по дате отправления: