From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | pg_restore --multi-thread |
Date: | 2009-02-12 15:41:01 |
Message-ID: | 200902121741.01937.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I know we've already had a discussion on the naming of the pg_restore -m
option, but in any case this description in pg_restore --help is confusing:
-m, --multi-thread=NUM use this many parallel connections to restore
Either it is using that many threads in the client, or it is using that many
connections to the server. I assume the implementation does approximately
both, but we should be clear about what we promise to the user. Either:
Reserve this many connections on the server. Or: Reserve this many threads
in the kernel of the client. The documentation in the reference/man page is
equally confused.
Also, the term "multi" is redundant, because whether it is multi or single is
obviously determined by the value of NUM.
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira de Oliveira | 2009-02-12 15:43:09 | Re: Which installation parts are backward compatible? |
Previous Message | Euler Taveira de Oliveira | 2009-02-12 15:27:03 | Re: Which installation parts are backward compatible? |