Re: [PATCHES] Patch for pg_dump: Multiple -t options and new -T option
От | Christopher Kings-Lynne |
---|---|
Тема | Re: [PATCHES] Patch for pg_dump: Multiple -t options and new -T option |
Дата | |
Msg-id | 410EF4C7.6020202@familyhealth.com.au обсуждение исходный текст |
Ответ на | Re: [PATCHES] Patch for pg_dump: Multiple -t options and new -T option (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: [PATCHES] Patch for pg_dump: Multiple -t options and new -T option
|
Список | pgsql-hackers |
Perhaps. I was also thinking that maybe it's time to combine pg_dumpall and pg_dump into a single utility. At the moment, I can't see how pg_dumpall can ever have a -Fc option, since it will be messy to interact with the pg_dump processes. I was thinking a pg_export utility that can output to a range of other databases SQL formats would also be a good idea. It would share about 90% of the pg_dump code, but I'm trying to think of how to avoid duplicating the code. How about we have a whole pg_dump/dumpall/restore/backup section in the TODO file? Chris Bruce Momjian wrote: > TODO item? > > --------------------------------------------------------------------------- > > Christopher Kings-Lynne wrote: > >>>>I just got an autoreply from David stating he will be away until August >>>>9 if we want this functionality we have to code it ourselves. If not it >>>>can wait until the next major release. >>> >>>It can wait --- it was submitted after feature freeze anyway, and we >>>certainly have more than enough other things to do in the next couple days. >> >>I have a plan to allow pg_dump to dump any object in the next version - >>i suspect these two ideas will need reconciliation. >> >>Chris >> > >
В списке pgsql-hackers по дате отправления: