idea - should the postgres copy path get a copy_insert/create method?

[jerch]

There is a possibility for a much faster copy_create alternative to bulk_create. From some initial tests that would be 10-20 times faster than the current implementation, but will have several restrictions/limitations - esp. the ID returning feature is hard to get done right (there might be workarounds possible from transaction id, not sure yet if thats a viable path).