Nick Fankhauser [EMAIL PROTECTED] writes:
Alvaro Herrera wrote:
The order is not really guaranteed, though if this is a one-shot thing,
you may get away with turning off hashed aggregates.
When I read this, I assumed there was a runtime parameter I could set that was
similar to
I have a table called Counties which partially contains a lot bad
data. By" bad data", I mean some records are missing; some exist and
shouldn't; and some records have fields with erroneous information.
However, the majority of the data in the table is accurate. I have
built/loaded a new table
Use Drop table
YOUR_TABLE cascade
Jhon CarrilloIngeniero en
ComputaciónCaracas - Venezuela
- Original Message -
From:
Mark
Fenbers
To: pgsql-sql@postgresql.org
Sent: Friday, May 13, 2005 2:38 PM
Subject: [SQL] Replacing a table with
constraints
I have a table
True, but Counties has about 8 or 9 rules, view, or pk constraints
attached to it. I don't want to break all these unless I knew of a way
to save off the SQL for them beforehand so I can easily rebuild them...
Mark
Ing. Jhon Carrillo wrote:
Use Drop
table YOUR_TABLE cascade
Are the constraints deferrable?
If they are, then you can replace the data with a single transaction.
If not, then you'll have to look at disabling triggers for the update.
On Fri, 2005-05-13 at 14:55, Mark Fenbers wrote:
True, but Counties has about 8 or 9 rules, view, or pk constraints
On Fri, 2005-05-13 at 14:38 -0400, Mark Fenbers wrote:
I have a table called Counties which partially contains a lot bad
data. By bad data, I mean some records are missing; some exist and
shouldn't; and some records have fields with erroneous information.
However, the majority of the data in
