From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Igor Korot <ikorot01(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Connection options |
Date: | 2017-06-15 20:13:40 |
Message-ID: | a39e360e-be6a-9650-fbdb-b363bb86bad4@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 06/15/2017 12:02 PM, Igor Korot wrote:
> Hi, again,
>
> On Thu, Jun 15, 2017 at 2:59 PM, Igor Korot <ikorot01(at)gmail(dot)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
>
> Thank you.
>
>>
>> Thank you.
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Gabriel Furstenheim Milerud | 2017-06-15 20:15:01 | Re: Freeing memory in native extension in case of error |
Previous Message | Tom Lane | 2017-06-15 20:07:46 | Re: Freeing memory in native extension in case of error |