Re: ecpglib use PQconnectdbParams - Mailing list pgsql-hackers

From Michael Meskes
Subject Re: ecpglib use PQconnectdbParams
Date
Msg-id 20120213112146.GA29242@feivel.credativ.lan
Whole thread Raw
In response to Re: ecpglib use PQconnectdbParams  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
> Because connect_timeout is a separate libpq connection parameter, but
> now it's stuck into "options".  It might have worked more or less by
> accident before.

So it is not an option, right? But the old function accepted it as an option it seems.

> It's not clear to me why this only appears on checktcp.  And why we
> don't run those tests by default.  That should be clarified, because

This was decided when regression tests for ecpg were introduced to not depend
on the use of TCP ports.

For details see this thread:
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00078.php
and in particular these emails:
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00118.php
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00134.php

Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at googlemail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Finer Extension dependencies
Next
From: Heikki Linnakangas
Date:
Subject: Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)