Re: parallel restore - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: parallel restore
Date
Msg-id 4986D0A2.4000600@gmx.net
Whole thread Raw
In response to Re: parallel restore  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: parallel restore  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Andrew Dunstan wrote:
>> Still, that's not a 100% solution because of the cases where we use
>> reconnections to change user IDs --- the required password would
>> (usually) vary.  It might be sufficient to forbid that case with
>> parallel restore, though; I think it's mostly a legacy thing anyway.
> 
> I didn't know such a thing even existed. What causes it to happen? I 
> agree it should be forbidden.

It was the only way to switch users before we had SET SESSION 
AUTHORIZATION and SET ROLE and such.  But the pg_restore man page says 
that -R/--no-reconnect is obsolete, so I'm not sure what the current 
behavior really is.


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Controlling hot standby
Next
From: Magnus Hagander
Date:
Subject: Re: mingw check hung