Re: Inserting large number of rows using libpq++ stops responding in c++

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Taz Master <tazmaster(at)rocketmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Inserting large number of rows using libpq++ stops responding in c++
Date: 2002-12-01 19:00:53
Message-ID: 27285.1038769253@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Taz Master <tazmaster(at)rocketmail(dot)com> writes:
> My only theory as to what might be causing this would be the large
> number of SQL commands executed before the commit. Is this right?

No. 100 inserts hardly qualifies as "a large number" -- people
routinely run transactions with many thousand commands.

I'm guessing a bug in your own code, though it's possible that libpq++
is the source of the problem.

If you have any other clients active at the same time, it's also
possible that there is no bug, and the thing is simply waiting for
a lock held by some other client. This would be more likely if you
have foreign keys in the table being inserted into --- foreign key
references take write-locks on the referenced rows.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rod Taylor 2002-12-01 19:04:21 Re: Hard-coded PUBLIC in pg_dump
Previous Message David Wheeler 2002-12-01 18:54:15 Re: Hard-coded PUBLIC in pg_dump