Bruce Momjian wrote: > Larry Rosenman wrote: >> Tom Lane wrote: >>> Bruce Momjian <pgman@candle.pha.pa.us> writes: >>>> I thought about this. Attached is a patch you can use to >>>> popen("pg_config") and then look for the thread flag to configure. >>>> One idea would be to add this sample to our libpq documentation. >>>> The problem with the example is popen() overhead, pg_config not in >>>> $PATH, or pg_config's version not matching libpq's version. >>> >>> Yeah, the last point seems like a killer objection :-(. It'd be >>> better to add some sort of libpq function to handle the issue. >>> >> >> and when I've proposed libpq functions to expose compile-time >> constants, I've been shot down. >> >> How is this different? > > No idea, what is the URL of your proposal. Keep in mind this is not > option-specific.
I had made a proposal to expose the path used for pg_service.conf. this was back a month or so ago. Would it be better to make a structure that has ALL the options, and return that from ONE function? If so, I can code it up. I have time available. -- Larry Rosenman Database Support Engineer PERVASIVE SOFTWARE. INC. 12365B RIATA TRACE PKWY 3015 AUSTIN TX 78727-6531 Tel: 512.231.6173 Fax: 512.231.6597 Email: [EMAIL PROTECTED] Web: www.pervasive.com ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster