Re: Upgrading rant.

Поиск
Список
Период
Сортировка
От Greg Copeland
Тема Re: Upgrading rant.
Дата
Msg-id 1041778067.15932.238.camel@mouse.copelandconsulting.net
обсуждение исходный текст
Ответ на Re: Upgrading rant.  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Upgrading rant.  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-hackers
On Sat, 2003-01-04 at 22:37, Tom Lane wrote:
> You're missing the point: I don't want to lock out everyone but the
> super-user, I want to lock out everyone, period.  Superusers are just
> as likely to screw up pg_upgrade as anyone else.
> 
> BTW:
> 
> $ postmaster -N 1 -c superuser_reserved_connections=1
> postmaster: superuser_reserved_connections must be less than max_connections.
> $
> 

Well, first, let me say that the above just seems wrong.  I can't think
of any valid reason why reserved shouldn't be allowed to equal max.  

I also assumed that pg_update would be attempting to connect as the
superuser.  Therefore, if you only allow a single connection from the
superuser and pg_upgrade is using it, that would seem fairly hard to
mess things up.  On top of that, that's also the risk of someone being a
superuser.  They will ALWAYS have the power to hose things.  Period.  As
such, I don't consider that to be a valid argument.



-- 
Greg Copeland <greg@copelandconsulting.net>
Copeland Computer Consulting



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

Предыдущее
От: Justin Clift
Дата:
Сообщение: Re: New Portal in Place, DNS switched ...
Следующее
От: Greg Copeland
Дата:
Сообщение: Re: [GENERAL] v7.3.1 Bundled and Released ...