| From: | Mark Rae <mrae(at)purplebat(dot)com> |
|---|---|
| To: | Nicolas Barbier <nicolas(dot)barbier(at)gmail(dot)com> |
| Cc: | Richard Huxton <dev(at)archonet(dot)com>, jeff sacksteder <jsacksteder(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: transaction limits? |
| Date: | 2005-10-21 11:17:32 |
| Message-ID: | 20051021111732.GA11147@purplebat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Oct 21, 2005 at 12:25:36PM +0200, Nicolas Barbier wrote:
> On 10/21/05, Richard Huxton <dev(at)archonet(dot)com> wrote:
> > jeff sacksteder wrote:
> > > Are there known limits to how many rows can be inserted by one transaction,
>
> > Well, the system will need to be able to roll back the transaction, ...
>
> Just by not indicating that a transaction did commit, others will keep
> ignoring its rows. There is nothing to rollback here, thanks to MVCC.
Also, I've just done 300 million row INSERTs, from a 'mysqldump', inside
a single transaction. So there doesn't appear to be any implementation
problems that would stop you from reaching the theoretical table limits.
-Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | han.holl | 2005-10-21 11:22:40 | Re: Strange order of execution with rule |
| Previous Message | Richard Huxton | 2005-10-21 11:07:53 | Re: transaction limits? |