Tom Lane wrote:
Alban Hertroys <[EMAIL PROTECTED]> writes:
It does have a reference to a table with statusses, but those are rather
static. I suppose an integrity check is comparable to doing a select
with respect to locking strategies? (Meaning that it wouldn't be the
cause of my problem).
No,
Alban Hertroys <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Alban Hertroys <[EMAIL PROTECTED]> writes:
>>> 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
Tom Lane wrote:
Alban Hertroys <[EMAIL PROTECTED]> 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.
Well, that's a relief. At least it means I'm not running i
Alban Hertroys <[EMAIL PROTECTED]> 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,
Is it possible that there is some limitation to the number of statements
in a single transaction? I'm trying to debug a problem where a program
locks up during an insert[*].
Actually, there are 3 simultaneous transactions going on, all doing
inserts of about 3000 records each. The problem occur
