From alnuwan@yahoo.com Fri Jan 25 19:55:40 2008 Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id ACBAB2E350F for ; Fri, 25 Jan 2008 15:55:40 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 66766-01-2 for ; Fri, 25 Jan 2008 15:55:37 -0400 (AST) Received: from web56411.mail.re3.yahoo.com (web56411.mail.re3.yahoo.com [216.252.111.90]) by postgresql.org (Postfix) with SMTP id 169762E022D for ; Fri, 25 Jan 2008 15:55:36 -0400 (AST) Received: (qmail 10820 invoked by uid 60001); 25 Jan 2008 19:55:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=0bWheE9ifYSiE0aryo9PBDX6pCO40taa/UqVyyBfZgE2QS5GlCmkYAMmYF5Ktrv/eVu5o1s6hOb9WdHGnxuuuORitj9vys0iJKCgttFkaG68Ql5TdSQmgKCJFAy0kHBbBzL32vPqovQtUOt6vckJoUEphiSs2zv+4wdmoCnd8H4=; X-YMail-OSG: EsMbDx0VM1nA_gxfN_auD657Hvz5ZD_.VZsJl6OPw.GN79NhzSeJJH7g1DPeSukaDY.9l_0euGPDdfOHqPd0MEweCoMNV0qCVaRJiRoijTEvNZDg9koCpuIFpw2iFKDMph1L1lpp9GtVu8fIKJNQkG7mVw-- Received: from [128.8.215.134] by web56411.mail.re3.yahoo.com via HTTP; Fri, 25 Jan 2008 11:55:35 PST Date: Fri, 25 Jan 2008 11:55:35 -0800 (PST) From: NUWAN LIYANAGE Subject: backup including symbolic links? To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1902456281-1201290935=:4964" Content-Transfer-Encoding: 8bit Message-ID: <256355.4964.qm@web56411.mail.re3.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/249 X-Sequence-Number: 28023 --0-1902456281-1201290935=:4964 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello, I have a 450gb production database, and was trying to create a development database using a bkp. I was following the instructions on postgres documentation, and came across the paragraph that says... " If you are using tablespaces that do not reside underneath this (data) directory, be careful to include them as well (and be sure that your backup dump archives symbolic links as links, otherwise the restore will mess up your tablespaces)." I have a seperate pg_tablespaces folder under E:\ drive since there wasn't enough space in my C:\ drive to put them. My db is 8.2 and is running on windows 2003. Can anyone tell me how to backup my database (including the symbolic links as links). Thank you Nuwan --------------------------------- Looking for last minute shopping deals? Find them fast with Yahoo! Search. --0-1902456281-1201290935=:4964 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello,

I have a 450gb production database, and was trying to create a development database using a bkp.
I was following the instructions on postgres documentation, and came across the paragraph that says...
" If you are using tablespaces that do not reside underneath this (data) directory, be careful to include them as well (and be sure that your backup dump archives symbolic links as links, otherwise the restore will mess up your tablespaces)."
I have a seperate pg_tablespaces folder under E:\ drive since there wasn't enough space in my C:\ drive to put them.

My db is 8.2 and is running on windows 2003.

Can anyone tell me how to backup my database (including the symbolic links as links).
Thank you
Nuwan


Looking for last minute shopping deals? Find them fast with Yahoo! Search. --0-1902456281-1201290935=:4964-- From scott.marlowe@gmail.com Sat Jan 26 02:23:03 2008 Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 743712E0045 for ; Fri, 25 Jan 2008 22:23:03 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 89850-10 for ; Fri, 25 Jan 2008 22:22:51 -0400 (AST) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by postgresql.org (Postfix) with ESMTP id 802752E0040 for ; Fri, 25 Jan 2008 22:22:59 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id m38so1529963waf.5 for ; Fri, 25 Jan 2008 18:22:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=CWldxrMK7up4ae9UeXu2J4DZ78WNVw2g+hD2be9svoo=; b=PxrHtUOrxGZwAZxwYST1qsv/2xdqZJy/ELr72WpsnvnjOFzSPEmE0GpJMWDPlrY/lsD+Oi1G8F75OLkyuYaIC7YrxZ3esL2K65njtrAavn3OmyNaGW9A9OB6e/DlfNs6s8rtCgLGEjPEEscphfyVXH+B9Ezmv44Q4+aDfBA+fSE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Q+7IacH6BpS9o5di7lMBm0qf1G4wGsjXGijG9vkW8CN+nIl6h+03Qtk7oL7yqgFXiBJOFy+bRb+szckWw4RG8kP3iHavE2Of7/w5nv+bhhneAgjySKmDlshU4TBCLteya3dd+Q2+NvvjDqAMXAsuk99Qdc51hDSZHKjUUd4YoVQ= Received: by 10.114.209.1 with SMTP id h1mr1106630wag.115.1201314178085; Fri, 25 Jan 2008 18:22:58 -0800 (PST) Received: by 10.114.133.5 with HTTP; Fri, 25 Jan 2008 18:22:58 -0800 (PST) Message-ID: Date: Fri, 25 Jan 2008 20:22:58 -0600 From: "Scott Marlowe" To: "NUWAN LIYANAGE" Subject: Re: backup including symbolic links? Cc: pgsql-admin@postgresql.org In-Reply-To: <256355.4964.qm@web56411.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <256355.4964.qm@web56411.mail.re3.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/256 X-Sequence-Number: 28030 On Jan 25, 2008 1:55 PM, NUWAN LIYANAGE wrote: > Hello, > > I have a 450gb production database, and was trying to create a development > database using a bkp. > I was following the instructions on postgres documentation, and came across > the paragraph that says... > " If you are using tablespaces that do not reside underneath this (data) > directory, be careful to include them as well (and be sure that your backup > dump archives symbolic links as links, otherwise the restore will mess up > your tablespaces)." > I have a seperate pg_tablespaces folder under E:\ drive since there wasn't > enough space in my C:\ drive to put them. > > My db is 8.2 and is running on windows 2003. > > Can anyone tell me how to backup my database (including the symbolic links > as links). A standard pg_dumpall --globals will dump the create tablespace statement, which you can edit as needed for your new machine. A plain pg_dump of the database will dump out the tables with tablespace statements. A pg_dumpall of the whole database cluster can also be used to do this. From alnuwan@yahoo.com Sat Jan 26 21:06:27 2008 Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 1EBBC2E00EE for ; Sat, 26 Jan 2008 17:06:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 94883-03 for ; Sat, 26 Jan 2008 17:05:58 -0400 (AST) Received: from web56414.mail.re3.yahoo.com (web56414.mail.re3.yahoo.com [216.252.111.93]) by postgresql.org (Postfix) with SMTP id ACBC02E007C for ; Sat, 26 Jan 2008 17:06:19 -0400 (AST) Received: (qmail 99232 invoked by uid 60001); 26 Jan 2008 21:06:18 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=QooIcT7SUmsnVTCljk763bcZlERLsQjcBbJJqBqCR+U0s+03fe3vBtmyXK7Ed5ly6qvbuPMUd6QW9JJrVdQHb4JtPO3D4MNOgCHFtzq9BFALqVeMY7wkhsrhVhzaK9TM1yxfMoX/EjnQnDcXoSYk1LeL2YDnY9Mksp/94H6iZ1I=; X-YMail-OSG: y2VsyloVM1n6VW_gY.kyeYezafHFHwsTgyI01MEQ5oqo7OxaIkZmCaToz4aJpAtK7nzfcDtOFh2lczaFrbEuh5xqanPx4bPf36ML8thn7Rf89RtW0oA- Received: from [208.73.110.242] by web56414.mail.re3.yahoo.com via HTTP; Sat, 26 Jan 2008 13:06:18 PST Date: Sat, 26 Jan 2008 13:06:18 -0800 (PST) From: NUWAN LIYANAGE Subject: Re: backup including symbolic links? To: Scott Marlowe Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1631176426-1201381578=:98499" Content-Transfer-Encoding: 8bit Message-ID: <447214.98499.qm@web56414.mail.re3.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/259 X-Sequence-Number: 28033 --0-1631176426-1201381578=:98499 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Yes, I was thinking of doing a pg_dumpall, but my only worry was that the singl file is going to be pretty large. I guess I don't have to worry too much about that. But my question to you sir is, If I want to create the development db using this pg dump file, how do I actually edit create tablespace statements so they will be created in the directory I want them to be. Or should I even worry about this.. (I want my data directory to be in E: drive including all the tablespaces.) Thank you very much for your reply. Nuwan. Scott Marlowe wrote: On Jan 25, 2008 1:55 PM, NUWAN LIYANAGE wrote: > Hello, > > I have a 450gb production database, and was trying to create a development > database using a bkp. > I was following the instructions on postgres documentation, and came across > the paragraph that says... > " If you are using tablespaces that do not reside underneath this (data) > directory, be careful to include them as well (and be sure that your backup > dump archives symbolic links as links, otherwise the restore will mess up > your tablespaces)." > I have a seperate pg_tablespaces folder under E:\ drive since there wasn't > enough space in my C:\ drive to put them. > > My db is 8.2 and is running on windows 2003. > > Can anyone tell me how to backup my database (including the symbolic links > as links). A standard pg_dumpall --globals will dump the create tablespace statement, which you can edit as needed for your new machine. A plain pg_dump of the database will dump out the tables with tablespace statements. A pg_dumpall of the whole database cluster can also be used to do this. ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster --------------------------------- Never miss a thing. Make Yahoo your homepage. --0-1631176426-1201381578=:98499 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Yes, I was thinking of doing a pg_dumpall, but my only worry was that the singl file is going to be pretty large. I guess I don't have to worry too much about that.
But my question to you sir is, If I want to create the development db using this pg dump file, how do I actually edit create tablespace statements so they will be created in the directory I want them to be. Or should I even worry about this.. (I want my data directory to be in E: drive including all the tablespaces.)
Thank you very much for your reply.
Nuwan.

Scott Marlowe <scott.marlowe@gmail.com> wrote:
On Jan 25, 2008 1:55 PM, NUWAN LIYANAGE wrote:
> Hello,
>
> I have a 450gb production database, and was trying to create a development
> database using a bkp.
> I was following the instructions on postgres documentation, and came across
> the paragraph that says...
> " If you are using tablespaces that do not reside underneath this (data)
> directory, be careful to include them as well (and be sure that your backup
> dump archives symbolic links as links, otherwise the restore will mess up
> your tablespaces)."
> I have a seperate pg_tablespaces folder under E:\ drive since there wasn't
> enough space in my C:\ drive to put them.
>
> My db is 8.2 and is running on windows 2003.
>
> Can anyone tell me how to backup my database (including the symbolic links
> as links).

A standard pg_dumpall --globals will dump the create tablespace
statement, which you can edit as needed for your new machine. A plain
pg_dump of the database will dump out the tables with tablespace
statements. A pg_dumpall of the whole database cluster can also be
used to do this.

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster


Never miss a thing. Make Yahoo your homepage. --0-1631176426-1201381578=:98499-- From scott.marlowe@gmail.com Sat Jan 26 22:30:39 2008 Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 8CCCA2E003D for ; Sat, 26 Jan 2008 18:30:39 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 16740-07 for ; Sat, 26 Jan 2008 18:30:34 -0400 (AST) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by postgresql.org (Postfix) with ESMTP id 99DAC2E0155 for ; Sat, 26 Jan 2008 18:30:33 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id m38so2117073waf.5 for ; Sat, 26 Jan 2008 14:30:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=wihfq1RJPx7dtICHLShkAfFVkVDPeMaW+YY1qqYJMhc=; b=jxEWyGhY+w5GlnFrjgHZsoGF68vaoIkQFuhG5uF1T3MjETedMQhAZ4u7+YwBAMbmdtibbwrFBsGzKjDb+QXiP0DcxbG+YLF6kMc63C5IC9QHi4Xk3Ej0H5989+ChMAYgcbe0cxAimu8prfi7RhMBri61TAjwIJL5WGDEehj29Ac= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ip7QUEUbeNF9InLtLDhBMBuNKlw6oot1UM3dHpHmEZg8Vgf7qRuzEJ7AWhMy7fajpXpe7cjDdapm3V7qusYkCIqgVfqR04I409PcxIwRQWZWM/PDC2Sh5L600hOzc0eEuuwcEpujU+bu08E89dX7rKN2NXaVCEfelksVWHIBsto= Received: by 10.115.58.1 with SMTP id l1mr26058wak.110.1201386632125; Sat, 26 Jan 2008 14:30:32 -0800 (PST) Received: by 10.114.133.5 with HTTP; Sat, 26 Jan 2008 14:30:32 -0800 (PST) Message-ID: Date: Sat, 26 Jan 2008 16:30:32 -0600 From: "Scott Marlowe" To: "NUWAN LIYANAGE" Subject: Re: backup including symbolic links? Cc: pgsql-admin@postgresql.org In-Reply-To: <447214.98499.qm@web56414.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <447214.98499.qm@web56414.mail.re3.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/260 X-Sequence-Number: 28034 On Jan 26, 2008 3:06 PM, NUWAN LIYANAGE wrote: > Yes, I was thinking of doing a pg_dumpall, but my only worry was that the > singl file is going to be pretty large. I guess I don't have to worry too > much about that. > But my question to you sir is, If I want to create the development db using > this pg dump file, how do I actually edit create tablespace statements so > they will be created in the directory I want them to be. Or should I even > worry about this.. (I want my data directory to be in E: drive including all > the tablespaces.) Take a look through the docs on pg_dump and pg_dumpall. A few of the options to look at are the ones to dump just data or just schema. Quite often you don't need the data, just the schema, for development. "pg_dump -s dbname" will dump just the schema, and "pg_dumpall --globals" will dump just the global database info, i.e. usernames, tablespaces, etc... Then just edit in your favorite text editor and point the resulting file(s) at your dev db with psql f mydump.sql where mydump.sql is the file you got from one or more of the above operations. After that, I highly recommend that any changes you wish to make, do so with .sql scripts (stored in your favorite version control system), so that you can then apply them to your production database later with minimal fuss. Note that any changes that should be "all or nothing" to the production database can be applied in a transaction (i.e. wrapped in a begin/commit pair) and then either all or none of the changes will be made... example begin; create table abc .... alter table xyz ... insert ... commit; if any of those commands fail (things like creating unique indexes might fail on production where they didn't in development) then no harm, no foul, just figure out what went wrong and update your script so it takes care of those problems. From alnuwan@yahoo.com Sun Jan 27 15:23:06 2008 Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 17C1A2E00C7 for ; Sun, 27 Jan 2008 11:23:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 74444-02 for ; Sun, 27 Jan 2008 11:22:54 -0400 (AST) Received: from web56405.mail.re3.yahoo.com (web56405.mail.re3.yahoo.com [216.252.111.84]) by postgresql.org (Postfix) with SMTP id 6ABE02E00AC for ; Sun, 27 Jan 2008 11:23:00 -0400 (AST) Received: (qmail 84037 invoked by uid 60001); 27 Jan 2008 15:22:58 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=Pc8U988OcFdAk8Nyku2tHYeHz9c2ArYdQUul/bM3KBzdzMAc0wMtaIZ6mA6KcugekJ9XvQehDb7jtxZ36j0eHcWbZ+BYxDNgiXwN/4D2FzI0yPSmVPeRYnjZrBCNsYu+SlPquNUXsQJai006bj3Rb2e7x4pfndevWb/wKRMihpw=; X-YMail-OSG: EbSNMUkVM1nKhu998afIKIWKyV2hIteT4Zru5q_E1iBNUQkLDO4C2zBqRjVVlzxV0T9jEchWiBWceW5HkWK7xWvrYhZk0YRPPdhV8VjiQeftD1NgT9CayPBgDICJHg-- Received: from [70.22.77.195] by web56405.mail.re3.yahoo.com via HTTP; Sun, 27 Jan 2008 07:22:58 PST Date: Sun, 27 Jan 2008 07:22:58 -0800 (PST) From: NUWAN LIYANAGE Subject: Re: backup including symbolic links? To: Scott Marlowe Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-381333013-1201447378=:83189" Content-Transfer-Encoding: 8bit Message-ID: <658738.83189.qm@web56405.mail.re3.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/262 X-Sequence-Number: 28036 --0-381333013-1201447378=:83189 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Thank you very much Scott.. I'll keep you updated on my progress. Thanks again. Nuwan. Scott Marlowe wrote: On Jan 26, 2008 3:06 PM, NUWAN LIYANAGE wrote: > Yes, I was thinking of doing a pg_dumpall, but my only worry was that the > singl file is going to be pretty large. I guess I don't have to worry too > much about that. > But my question to you sir is, If I want to create the development db using > this pg dump file, how do I actually edit create tablespace statements so > they will be created in the directory I want them to be. Or should I even > worry about this.. (I want my data directory to be in E: drive including all > the tablespaces.) Take a look through the docs on pg_dump and pg_dumpall. A few of the options to look at are the ones to dump just data or just schema. Quite often you don't need the data, just the schema, for development. "pg_dump -s dbname" will dump just the schema, and "pg_dumpall --globals" will dump just the global database info, i.e. usernames, tablespaces, etc... Then just edit in your favorite text editor and point the resulting file(s) at your dev db with psql f mydump.sql where mydump.sql is the file you got from one or more of the above operations. After that, I highly recommend that any changes you wish to make, do so with .sql scripts (stored in your favorite version control system), so that you can then apply them to your production database later with minimal fuss. Note that any changes that should be "all or nothing" to the production database can be applied in a transaction (i.e. wrapped in a begin/commit pair) and then either all or none of the changes will be made... example begin; create table abc .... alter table xyz ... insert ... commit; if any of those commands fail (things like creating unique indexes might fail on production where they didn't in development) then no harm, no foul, just figure out what went wrong and update your script so it takes care of those problems. --------------------------------- Looking for last minute shopping deals? Find them fast with Yahoo! Search. --0-381333013-1201447378=:83189 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Thank you very much Scott..
I'll keep you updated on my progress.
Thanks again.
Nuwan.

Scott Marlowe <scott.marlowe@gmail.com> wrote:
On Jan 26, 2008 3:06 PM, NUWAN LIYANAGE wrote:
> Yes, I was thinking of doing a pg_dumpall, but my only worry was that the
> singl file is going to be pretty large. I guess I don't have to worry too
> much about that.
> But my question to you sir is, If I want to create the development db using
> this pg dump file, how do I actually edit create tablespace statements so
> they will be created in the directory I want them to be. Or should I even
> worry about this.. (I want my data directory to be in E: drive including all
> the tablespaces.)

Take a look through the docs on pg_dump and pg_dumpall.

A few of the options to look at are the ones to dump just data or just
schema. Quite often you don't need the data, just the schema, for
development. "pg_dump -s dbname" will dump just the schema, and
"pg_dumpall --globals" will dump just the global database info, i.e.
usernames, tablespaces, etc...

Then just edit in your favorite text editor and point the resulting
file(s) at your dev db with psql f mydump.sql where mydump.sql is the
file you got from one or more of the above operations.

After that, I highly recommend that any changes you wish to make, do
so with .sql scripts (stored in your favorite version control system),
so that you can then apply them to your production database later with
minimal fuss.

Note that any changes that should be "all or nothing" to the
production database can be applied in a transaction (i.e. wrapped in a
begin/commit pair) and then either all or none of the changes will be
made...

example
begin;
create table abc ....
alter table xyz ...
insert ...
commit;

if any of those commands fail (things like creating unique indexes
might fail on production where they didn't in development) then no
harm, no foul, just figure out what went wrong and update your script
so it takes care of those problems.


Looking for last minute shopping deals? Find them fast with Yahoo! Search. --0-381333013-1201447378=:83189--