Re: [GENERAL] Connection options - Mailing list pgsql-general

From Igor Korot
Subject Re: [GENERAL] Connection options
Date
Msg-id CA+FnnTwhy5B5fRBU2F_B2MvAzJtiz4c5CL28Bb_GKGBCHdzofA@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] Connection options  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: [GENERAL] Connection options
Re: [GENERAL] Connection options
List pgsql-general
Hi, Adrian,

On Thu, Jun 15, 2017 at 4:13 PM, Adrian Klaver
<adrian.klaver@aklaver.com> wrote:
> On 06/15/2017 12:02 PM, Igor Korot wrote:
>>
>> Hi, again,
>>
>> On Thu, Jun 15, 2017 at 2:59 PM, Igor Korot <ikorot01@gmail.com> wrote:
>>>
>>>   Hi, ALL,
>>> I'm looking at the documentation at
>>> www.postgresql.org/docs/current/static/libpq-connect.html
>>> section 32.1.2.
>>>
>>> The part for "option" reads:
>>>
>>> [quote]
>>> Specifies command-line options to send to the server...
>>> [/quote]
>>>
>>> Does this mean that if I'm writing a C/C++ program, I shouldn't care
>>> about that?
>>> Or there are legitimate set of options I can set to pass to
>>> PQconnectDB()?
>>
>>
>> In addition:
>>
>> Where can I get a list of client encoding I can pass on the connection
>> to the server?
>
>
> https://www.postgresql.org/docs/9.6/static/multibyte.html

Is it possible to update the libpq-connect page with this link?

And could you clarify on the first part of this?
From the quote I poste it sounds like this is available only in command-line
tools. And if someone will use it inside the program it will be ignored.

Thank you.

>
>>
>> Thank you.
>>
>>>
>>> Thank you.
>>
>>
>>
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Gabriel Furstenheim Milerud
Date:
Subject: Re: [GENERAL] Freeing memory in native extension in case of error
Next
From: Adrian Klaver
Date:
Subject: Re: [GENERAL] Connection options