Re: [HACKERS] CHECK constraints in pg_dump

2003-02-26 Thread Tom Lane
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes: >> Why would there be any speed advantage? > Is it not faster to add it when all the data is there, rather than > evaluating it as each row is inserted, like indexes? I don't see why. There are good algorithmic reasons why bulk-loading an ind

Re: [HACKERS] CHECK constraints in pg_dump

2003-02-25 Thread Christopher Kings-Lynne
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes: > > I notice that we're still dumping CHECK constraints as part of the CREATE > > TABLE statement, and not as an ALTER TABLE statement after the data has been > > loaded. > > > Should we move it to after the data for speed purposes, like we h

Re: [HACKERS] CHECK constraints in pg_dump

2003-02-25 Thread Tom Lane
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes: > I notice that we're still dumping CHECK constraints as part of the CREATE > TABLE statement, and not as an ALTER TABLE statement after the data has been > loaded. > Should we move it to after the data for speed purposes, like we have with > a

[HACKERS] CHECK constraints in pg_dump

2003-02-25 Thread Christopher Kings-Lynne
Hi guys, I notice that we're still dumping CHECK constraints as part of the CREATE TABLE statement, and not as an ALTER TABLE statement after the data has been loaded. Should we move it to after the data for speed purposes, like we have with all other constraints? Chris --