pg_pwd trigger to be removed

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема pg_pwd trigger to be removed
Дата
Msg-id Pine.LNX.4.21.0003051422190.347-100000@localhost.localdomain
обсуждение исходный текст
Ответы Re: [HACKERS] pg_pwd trigger to be removed
Re: [HACKERS] pg_pwd trigger to be removed
Список pgsql-hackers
Because of the problems that were pointed out, I'm inclined to remove the
pg_pwd updating trigger again. I can offer you the non-initdb requiring
variant (just remove the trigger definition in initdb) or the
clean-sweeping one (remove the trigger function from the backend). Okay,
the first one will require some sort of intervention as well, eventually,
but you see the difference.

My new take on the situation is actually that there shouldn't be a reason
to tinker with the systems catalogs period. In the case of pg_shadow
that's not entirely possible (catupd and trace can't be adjusted
otherwise), but that can be fixed (not now). After all they're called
*system* catalogs. If someone thinks they can rename a table by updating
pg_class.relname -- good night!

-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Brian Hirt
Дата:
Сообщение: Optimizer badness in 7.0 beta
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] DROP TABLE inside a transaction block