Re: vacuum locking

Поиск
Список
Период
Сортировка
От Rob Nagler
Тема Re: vacuum locking
Дата
Msg-id 16281.41629.69000.492473@gargle.gargle.HOWL
обсуждение исходный текст
Ответ на Re: vacuum locking  (Mario Weilguni <mweilguni@sime.com>)
Ответы Re: vacuum locking  (Greg Stark <gsstark@mit.edu>)
Список pgsql-performance
Mario Weilguni writes:
> of course both approaches have advantages, it simply depends on the usage
> pattern. A case where oracle really rules over postgresql are m<-->n
> connection tables where each record consist of two foreign keys, the
> overwrite approach is a big win here.

That's usually our case.  My company almost always has "groupware"
problems to solve.  Every record has a "realm" (security) foreign key
and typically another key.  The infrastructure puts the security
key on queries to avoid returning the wrong realm's data.

Rob



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

Предыдущее
От: Rob Nagler
Дата:
Сообщение: Re: vacuum locking
Следующее
От: Rob Nagler
Дата:
Сообщение: Re: vacuum locking