Clinging to sanity, [EMAIL PROTECTED] (Tom Lane) mumbled into her beard: > ow <[EMAIL PROTECTED]> writes: >> My concern though ... wouldn't pgSql server collapse when faced with >> transaction spawning across 100M+ records? > > No. You're extrapolating from Oracle-specific assumptions again.
Or from MySQL-specific assumptions :-). It seems reasonable (absent of particular knowledge to the contrary) that the size of a transaction might be _expected_ to be some sort of constraint; it is quite surprising that it isn't, and I don't think that's purely based on the mistake of assuming that the whole world does things exactly like Oracle. -- (format nil "[EMAIL PROTECTED]" "cbbrowne" "acm.org") http://cbbrowne.com/info/postgresql.html Rules of the Evil Overlord #89. "After I captures the hero's superweapon, I will not immediately disband my legions and relax my guard because I believe whoever holds the weapon is unstoppable. After all, the hero held the weapon and I took it from him." <http://www.eviloverlord.com/> ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
