Re: pg_upgrade improvements
От | Tom Lane |
---|---|
Тема | Re: pg_upgrade improvements |
Дата | |
Msg-id | 4724.1333642368@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pg_upgrade improvements (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: pg_upgrade improvements
|
Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes: > On Thursday, April 05, 2012 05:39:19 PM Tom Lane wrote: >> Yeah, that would be a small pain in the neck, but it eliminates a huge >> pile of practical difficulties, like your blithe assumption that you can >> find a "private directory" somewhere (wrong) or disallow access to other >> people (also wrong, if they are using the same account as you). > I don't think this needs to protect against malicious intent of a user running > with the *same* privileges as the postmaster. Who said anything about malicious intent? Please re-read the original gripe in this thread. There's nothing un-legitimate about, eg, clients trying to connect to the database during your maintenance window. What we want is to be sure that nobody can connect to the database except the person running the standalone instance. To my mind "sure" means "sure"; it does not include qualifiers like "unless some other process tries to do the same thing at about the same time". regards, tom lane
В списке pgsql-hackers по дате отправления: