Well... I assumed that'd be the case; production dumps are not small... this calls for some scripting stuff; the script should basically the steps mentioned above, and you will have a trimmed down version of the dump file... :)
But again, the script should be fast enough to make this additional step look smaller than the time required to restore+drop unwanted DBs. Best regards, On Feb 4, 2008 5:10 PM, Guido Neitzer <[EMAIL PROTECTED]> wrote: > On 04.02.2008, at 18:00, Gurjeet Singh wrote: > > > I understand it all needs a little bit of 'vi' wizardry, (or > > whichever editor you are using). Also, as with all open-source > > suggestions, do not rely on this procedure until you understand what > > and how it does what it does. > > Sure, the only problem is, I'm talking about a laaaarge file. Maybe I > just import the whole bunch and drop some of the databases after that. > Seems to be less hazzle, but takes probably an hour or two longer, so > I'll take a service window next night ... > > Thanks for the hints. > > cug > -- [EMAIL PROTECTED] [EMAIL PROTECTED] gmail | hotmail | indiatimes | yahoo }.com EnterpriseDB http://www.enterprisedb.com 17° 29' 34.37"N, 78° 30' 59.76"E - Hyderabad 18° 32' 57.25"N, 73° 56' 25.42"E - Pune 37° 47' 19.72"N, 122° 24' 1.69" W - San Francisco * http://gurjeet.frihost.net Mail sent from my BlackLaptop device
