Karsten Hilbert wrote:
On Sun, Oct 07, 2007 at 09:04:01PM -0400, Dave Cramer wrote:
That is more efficient, however postgresql will still check the integrity
of the data. Now that I think of it, if you look at the dumps postgresql
creates, it applies the FK constraint after inserting all the data.
Note: I'm not suggesting that you drop them, I'm just suggesting that
sometimes compromises must be made between the "right" answer and the
practical solution.
Well, we haven't yet encountered a scenario where things
were too slow due to FKs so the decision wasn't necessary
yet.
There's also the first rule of optimization: Don't.
The second: Don't yet.
We applied it so far.
Yeah, I'd have to agree with that adage. Of course one could argue that
XMIN is a premature optimization.
as far as postgresql goes the new HOT patch comes dangerously close to
changing the semantics of XMIN.
Dave
Karsten
_______________________________________________
Gnumed-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnumed-devel
