Re: Table data exclusion patch for pg_dump
От
Tom Lane
Тема
Re: Table data exclusion patch for pg_dump
Дата
Msg-id
22744.1241207429@sss.pgh.pa.us
Ответ на
Re: Table data exclusion patch for pg_dump (Andrew Dunstan)
Список
Дерево обсуждения
Table data exclusion patch for pg_dump Vadim Trochinsky <me@vadim.ws>
Re: Table data exclusion patch for pg_dump Tom Lane <tgl@sss.pgh.pa.us>
Re: Table data exclusion patch for pg_dump Andrew Dunstan <andrew@dunslane.net>
Re: Table data exclusion patch for pg_dump Tom Lane <tgl@sss.pgh.pa.us>
Re: Table data exclusion patch for pg_dump Pavel Stehule <pavel.stehule@gmail.com>
Re: Table data exclusion patch for pg_dump Andrew Dunstan <andrew@dunslane.net>
Re: Table data exclusion patch for pg_dump Tom Lane <tgl@sss.pgh.pa.us>
Re: Table data exclusion patch for pg_dump Jaime Casanova <jcasanov@systemguards.com.ec>
Re: Table data exclusion patch for pg_dump Asko Oja <ascoja@gmail.com>
Andrew Dunstan writes: > Well, you can shoot yourself in the foot using pg_restore's --use-list > option too, but that doesn't mean it's not useful. And indeed it could > be used to achieve the OP's ends, except that he would have spent > useless time and space dumping the data for a table he doesn't want. The critical difference, of course, being that when he discovers that it doesn't work, he *has got* the data he needs to have to perform the restore. Excluding data at dump time is considerably more dangerous because of the likelihood that you won't have any recourse when you need it. (In which connection, it is an astonishingly bad idea to repurpose -d and -D for this behavior, so soon after we deprecated them.) regards, tom lane
В списке pgsql-hackers по дате отправления