Re: idle in transaction query makes server unresponsive - Mailing list pgsql-general

From Albe Laurenz
Subject Re: idle in transaction query makes server unresponsive
Date
Msg-id D960CB61B694CF459DCFB4B0128514C20874C0AE@exadv11.host.magwien.gv.at
Whole thread Raw
In response to Re: idle in transaction query makes server unresponsive  (Scot Kreienkamp <SKreien@la-z-boy.com>)
Responses Re: idle in transaction query makes server unresponsive  (Chris Travers <chris.travers@gmail.com>)
List pgsql-general
Scot Kreienkamp wrote:
>> You could try to "strace" the postmaster during a connection attempt
>> and see what happens.  Maybe that helps to spot the place where
>> things go wrong.

> [Scot Kreienkamp]
> I'm willing to give it a try, but I've never done it before.  What do
I need to do?

"man strace" is your friend.  Assuming you are on Linux.

Find out the process ID of the postmaster process
(the parent of the other PostgreSQL processes),
then try

strace -f -o /some/large/directory/tracefile -p process_id

The connect to PostgreSQL and see what gets logged.

Press Ctrl+C to stop strace.

Yours,
Laurenz Albe


pgsql-general by date:

Previous
From: Andres Freund
Date:
Subject: Re: Memory issues
Next
From: Chris Travers
Date:
Subject: Re: idle in transaction query makes server unresponsive