Re: On file locking

Поиск
Список
Период
Сортировка
Искать
От
Kevin Brown
Тема
Re: On file locking
Дата
Msg-id
20030201171145.GQ12957@filer
Ответ на
Список
Дерево обсуждения
On file locking Kevin Brown <kevin@sysexperts.com>
Re: On file locking Rod Taylor <rbt@rbt.ca>
Re: On file locking Tom Lane <tgl@sss.pgh.pa.us>
Re: On file locking Kevin Brown <kevin@sysexperts.com>
Re: On file locking "Shridhar Daithankar<shridhar_daithankar@persistent.co.in>" <shridhar_daithankar@persistent.co.in>
Re: On file locking Curt Sampson <cjs@cynic.net>
Re: On file locking Kevin Brown <kevin@sysexperts.com>
Re: On file locking Tom Lane <tgl@sss.pgh.pa.us>
Re: On file locking Kevin Brown <kevin@sysexperts.com>
Re: On file locking Antti Haapala <antti.haapala@iki.fi>
Re: On file locking Antti Haapala <antti.haapala@iki.fi>
Re: On file locking Tom Lane <tgl@sss.pgh.pa.us>
Re: On file locking Curt Sampson <cjs@cynic.net>
Re: On file locking "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
Tom Lane wrote:
> Kevin Brown  writes:
> > So if we wanted to make use of mandatory locks, we'd have to refrain
> > from using flock().
> 
> We have no need for mandatory locks; the advisory style will do fine.
> This is true because we have no desire to interoperate with any
> non-Postgres code ... everyone else is supposed to stay the heck out of
> $PGDATA.

True.  But, of course, mandatory locks could be used to *make*
everyone else stay out of $PGDATA.  :-)


-- 
Kevin Brown					      kevin@sysexperts.com

В списке pgsql-hackers по дате отправления
От: Greg Copeland
Дата:
От: Kevin Brown
Дата:
Сообщение: Re: sync()
FAQ