RE: Postgre7.0.2 drop user bug

Поиск
Список
Период
Сортировка
От Matthew
Тема RE: Postgre7.0.2 drop user bug
Дата
Msg-id 183FA749499ED311B6550000F87E206C0C93E9@srv.ctlno.com
обсуждение исходный текст
Ответ на Postgre7.0.2 drop user bug  (Matthew <matt@ctlno.com>)
Ответы Re: Postgre7.0.2 drop user bug  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
>-----Original Message-----
>From: Tom Lane

>The correct fix is CommandCounterIncrement() in the DROP USER loop,
>so that later iterations can see the changes made by prior iterations.
>
>            regards, tom lane

Since postgre now suppport referential integrity and cascading deletes,
wouldn't it make more sense to use that code to manage the relationship
between pg_user and pg_group (and probably a wealth of other system tables),
rather then having to write specific code to manage every relationship
between system tables, or are those types of constraints just not applicable
to system tables?


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

Предыдущее
От: Matthew
Дата:
Сообщение: RE: Postgre7.0.2 drop user bug
Следующее
От: Thomas Lockhart
Дата:
Сообщение: Re: Re: pg_dump docs