Yeah understand that, but I'm trying to figure out why it is taking too long. there is foreign key relation to this table.
Thanks,
Rj
On Friday, April 9, 2021, 02:16:08 AM PDT, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Thu, 2021-04-08 at 20:14 +0000, Nagaraj Raj wrote:
> We are trying to load data around 1Bil records into one table with INSERT statements > (not able to use COPY command) and they are been waiting for a lock and the wait_event > is "transactionid", I didn't find any information in the documents. Queries have been > waiting for hours.
That means that your statement is stuck behind a row lock.
Row locks are stored on the table row itself and contain the transaction ID. So the process has to wait until the transaction goes away, which is implemented as waiting for a lock on the transaction ID.
There must be a long running transaction that locks a row that is needed for the INSERT. It could be a row in a different table that is referenced by a foreign key.
Make that long running transaction go away. Transactions should never last that long.
