From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Harold Giménez <harold(dot)gimenez(at)gmail(dot)com> |
Subject: | Re: pg_upgrade improvements |
Date: | 2012-04-05 16:04:32 |
Message-ID: | 201204051804.32537.andres@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thursday, April 05, 2012 05:39:19 PM Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> >> The point is to avoid the risk that someone else could connect to the
> >> database at the same time you're doing work on it.
> >
> > I got that. I just fail to see what the advantage of using two pipes
> > instead of one socket as every other plain connection would be?
>
> 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. That one can simply delete the
whole cluster anyway. For everybody else you can just create a directory in
PGDATA and revoke all permissions on it for everybody but the owner.
For named pipes you could just create a random name with permissions only for
the current user (thats possible in the same call) and be done with it.
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-04-05 16:12:48 | Re: pg_upgrade improvements |
Previous Message | Jeff Janes | 2012-04-05 15:51:06 | Re: Publish checkpoint timing and sync files summary data to pg_stat_bgwriter |