From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Amir Abdollahi <amirabd2130(at)yahoo(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Connection Problem |
Date: | 2011-08-14 17:02:49 |
Message-ID: | 27920.1313341369@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Amir Abdollahi <amirabd2130(at)yahoo(dot)com> writes:
> I'm trying to add audit capability to Postgresql server. When the
> Postgresql server starts up, the server will start audit functions as
> a new subprocess thus the server will have 5 subprocesses instead of 4.
That doesn't sound like it's going to lead to a very well-performing
design, but I digress.
> Problem is that when I tried to connect to server [using libpq interface] I've always get this message:
> "canceling authentication due to timeout",
If you added any locking into the authentication transaction, maybe you
are getting bit by the same bug I just fixed:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=592b615d71caac8a3504276a805a6fd024c40041
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-08-14 17:11:01 | Re: our buffer replacement strategy is kind of lame |
Previous Message | Tom Lane | 2011-08-14 16:15:43 | Re: VACUUM FULL versus TOAST |