That seems like a rather spectacular overstatement of the likely
benefits, not to mention a misdescription of what was discussed.
AFAIR what was discussed was separating
Yes, that is what was discussed.
- schema stuff needed before loading data
- table data
- schema stuff needed after loading data
where the last category boils down to "indexes and then foreign keys".
All the "other stuff" such as functions really needs to be in the
first part ... or at least there's no visible benefit to delaying
loading it.
Right. This breakdown I still think would be useful. An additional item
that would be useful is to allow pg_restore to restore plain text dumps.
Sincerely,
Joshua D. Drake
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
