Re: parallel restore - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: parallel restore
Date
Msg-id 498369F1.6070106@dunslane.net
Whole thread Raw
In response to Re: parallel restore  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: parallel restore  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: parallel restore  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>   
>> Tom Lane wrote:
>>     
>>> One thing that is bothering me is that
>>> if the connection parameters are such as to cause prompts for passwords,
>>> it's going to be broken beyond usability (multiple threads all trying
>>> to read the terminal at once).  Is there anything we can do about that?
>>>       
>
>   
>> I thought I had put in changes to cache the password, so you shouldn't 
>> get multiple prompts.
>>     
>
> Ah, you can tell I hadn't gotten to the bottom of the patch yet ;-).
> 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.

cheers

andrew


pgsql-hackers by date:

Previous
From: Sam Mason
Date:
Subject: Re: using composite types in insert/update
Next
From: Tom Lane
Date:
Subject: Re: array_map not SQL accessible?