| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: options in conninfo |
| Date: | 2005-03-14 08:10:38 |
| Message-ID: | 6452.1110787838@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>>> Using libpq PQconnect function, what is the syntax for the 'options'
>>> entry in the conninfo?
>> I think it's stuck straight into the backend command line, so whatever
>> you read in the 'postgres' reference page applies.
> Oh, I thought it was for setting GUCs at connect time. Is that
> possible? I thought it was in the new protocol, but I just cannot find
> the docs on it...
No, the 'options' thing is exceedingly ancient. Try something like
PGOPTIONS="-fn" psql mydb
or equivalently
PGOPTIONS="-c enable-mergejoin=false" psql mydb
The GUC-at-connect-time feature is new in the V3 protocol. Offhand I do
not think libpq exposes that to its users; it does use it internally
IIRC.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Miroslav Šulc | 2005-03-14 08:43:19 | Re: [PERFORM] How to read query plan |
| Previous Message | Christopher Kings-Lynne | 2005-03-14 08:04:08 | Re: options in conninfo |