Re: multiple threads inserting into the same table

From: Tom Lane
Subject: Re: multiple threads inserting into the same table
Date: ,
Msg-id: 4396.1237849054@sss.pgh.pa.us
(view: Whole thread, Raw)
In response to: Re: multiple threads inserting into the same table  (Scott Marlowe)
List: pgsql-performance

Tree view

multiple threads inserting into the same table  (Brian Cox, )
 Re: multiple threads inserting into the same table  (David Wilson, )
 Re: multiple threads inserting into the same table  (Tom Lane, )
 Re: multiple threads inserting into the same table  (Brian Cox, )
  Re: multiple threads inserting into the same table  (Scott Marlowe, )
   Re: multiple threads inserting into the same table  (Tom Lane, )
  Re: multiple threads inserting into the same table  (Tom Lane, )
 Re: multiple threads inserting into the same table  (Brian Cox, )
 Re: multiple threads inserting into the same table  (Brian Cox, )

Scott Marlowe <> writes:
> On Mon, Mar 23, 2009 at 2:25 PM, Brian Cox <> wrote:
>> This generates and executes a single SQL insert. Since, as you point out,
>> postgres seems to think that this transaction isn't doing anything,
>> it's hard to figure out what the read is doing.

> Might you have a firewall that's killing the connections?  What does
> netstat -an on the client side say about these connections?

netstat will probably say the connection is open on both sides ---
otherwise the sockets would have closed.  It looks like both sides
still think the connection is open.  A firewall timeout is still
a possibility, but you'd have had to have a fairly long idle time
for that to happen.  Are any of the threads issuing commands that might
have run for very long intervals (tens of minutes)?

            regards, tom lane


pgsql-performance by date:

From: Tom Lane
Date:
Subject: Re: Why creating GIN table index is so slow than inserting data into empty table with the same index?
From: Kouber Saparev
Date:
Subject: Re: LIMIT confuses the planner