From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-sql@postgresql.org
Subject: Re: Programatically switching database
Date: Sun, 16 Nov 2003 10:22:31 -0500
Message-ID: <m3u154fidk.fsf@wolfe.cbbrowne.com> (raw)
References: <20031116051842.57962.qmail@web21404.mail.yahoo.com>
<26172.1068994367@sss.pgh.pa.us>
Clinging to sanity, tgl@sss.pgh.pa.us (Tom Lane) mumbled into her beard:
> ow <oneway_111@yahoo.com> 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 "~S@~S" "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/;
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: cbbrowne@acm.org
Subject: Re: Programatically switching database
In-Reply-To: <m3u154fidk.fsf@wolfe.cbbrowne.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox