Re: [COMMITTERS] pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary)

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [COMMITTERS] pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary)
Дата
Msg-id Pine.LNX.4.21.0007042325530.3542-100000@localhost.localdomain
обсуждение исходный текст
Ответы Re: [COMMITTERS] pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Tom Lane writes:

> but if one or both postmasters is started without -i then there's got
> to be some interlock on the Unix socket file.
> 
> I don't much like depending on flock for that, since it isn't available
> everywhere.  The only portable answer is to build a pid-containing
> interlock file for each socket file, as discussed in the TODO item.

But the flock code isn't used because the configure test for it is broken,
and has been broken ever since it was introduced AFAICT. It seems that we
have been relying on the mere existence of the socket file.


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



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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: [GENERAL] Revised Copyright: is this more palatable?
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Repair plan for inet and cidr types