Re: [HACKERS] postmaster crash and .s.pgsql file

Поиск
Список
Период
Сортировка
От Brook Milligan
Тема Re: [HACKERS] postmaster crash and .s.pgsql file
Дата
Msg-id 199801291910.MAA25411@trillium.nmsu.edu
обсуждение исходный текст
Ответ на Re: [HACKERS] postmaster crash and .s.pgsql file  (Bruce Momjian <maillist@candle.pha.pa.us>)
Ответы Re: [HACKERS] postmaster crash and .s.pgsql file  (The Hermit Hacker <scrappy@hub.org>)
Re: [HACKERS] postmaster crash and .s.pgsql file  (Bruce Momjian <maillist@candle.pha.pa.us>)
Список pgsql-hackers
> No.  Make /var/run writable by some group (e.g., group pidlog) and put
> postgres (and other things like root or daemon or ..., whatever needs
> to log pid files) in that group.

   We can't expect the user to be able to change /var/run permissions.
   Must be in pgsql/ or /tmp.

No, "normal" users shouldn't be allowed to do so, obviously.  But, are
there real systems in which a database maintainer (i.e., user
postgres) cannot cooperate with the system admin (i.e., user root) to
accomplish this?  In practice, is it really envisioned that postgres
should be _so_ distinct from the system?  For example, don't most
people run the postmaster from the system startup scripts, and isn't
that the same thing?  How did those commands get inserted into the
startup scripts if not by root?

Cheers,
Brook

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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [HACKERS] Error in nodes/parse_node.h
Следующее
От: The Hermit Hacker
Дата:
Сообщение: Re: [HACKERS] postmaster crash and .s.pgsql file