Re: parallel restore - Mailing list pgsql-hackers

From Tom Lane
Subject Re: parallel restore
Date
Msg-id 28409.1233348621@sss.pgh.pa.us
Whole thread Raw
In response to Re: parallel restore  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: parallel restore  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
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.

>> Also, how does this interact with single_txn mode?

> Yes. I thought I had done that too, will check.

Yeah, found that too.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: using composite types in insert/update
Next
From: Sam Mason
Date:
Subject: Re: using composite types in insert/update