"Tom Lane" <[EMAIL PROTECTED]> writes: > I think a sane way to think about what Simon would like to accomplish > is not "turn psql into a parallel job scheduler" but "teach pg_restore > how to do parallel scheduling, and then see if it can be made to do > anything useful with plain-text instead of archive-dump input". > At least that way you're talking about something that's within the scope > of the program's purpose.
Er, yes, that's what I meant. My point though was just that for single commands which take a long time to run on the server there's no additional work in the client needed to handle it. That is, as opposed to handling multiple COPYs in parallel where psql has to be involved in the actual data transfer and so you need multiple client as well as server processes. I think I'm sorry I got involved here though since I specifically do not have either the full context of this discussion or any background in pg_dump/pg_restore code. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
