Igor Korot <ikorot01@gmail.com> writes:
> On Thu, Jun 15, 2017 at 4:46 PM, David G. Johnston
> <david.g.johnston@gmail.com> wrote:
>> The options you pass from the client via the "options" attribute are
>> interpreted by *the server* as command-line options. They are not options
>> that control libpq itself.
> Can you give an example or try to explain it?
> What do you mean by "interpreted by the server as command-line options"?
See the switches described in
https://www.postgresql.org/docs/current/static/app-postgres.html
The point of the libpq "options" argument is that you can pass server
settings using that same switch syntax, for settings you'd be allowed to
change at runtime. This is obsolete legacy stuff; all of the available
options can be set with SET commands, and that's the preferred way to do
it now.
regards, tom lane