| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alban Hertroys <alban(at)magproductions(dot)nl> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Transaction size |
| Date: | 2005-01-07 17:21:29 |
| Message-ID: | 27308.1105118489@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alban Hertroys <alban(at)magproductions(dot)nl> writes:
> Is it possible that there is some limitation to the number of statements
> in a single transaction?
2^32, and if you'd exceeded it, you'd get a very specific error message
saying so.
> As they're inserts, and therefore not even touching the same data, I'm
> quite certain it's not some kind of row locking issue (does that even
> happen at all with MVCC?).
I'm not. In particular this could be a foreign key locking issue ---
does the target table have foreign keys, and if so could inserts from
different transactions be referencing the same master row?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Turner | 2005-01-07 17:57:01 | Re: does "select count(*) from mytable" always do a seq scan? |
| Previous Message | Culley Harrelson | 2005-01-07 17:09:49 | Re: does "select count(*) from mytable" always do a seq scan? |