| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: Let's remove psqlodbc option for geqo |
| Date: | 2014-11-02 14:41:55 |
| Message-ID: | CAB7nPqRFL6XYYn1E=0DMZvN0Hbv_N4EOugsx3hFDqTtsNfby=A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On Thu, Oct 30, 2014 at 2:55 AM, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com
> wrote:
> In the spirit of a spring cleanup, I think we should remove the psqlodbc
> configuration option for disabling geqo. I'm sure that's sometimes useful,
> but so are dozens of other backend GUGs. We have a generic "connection
> settings" field in the configuration that you can use if you really need to
> disable qego.
>
> Any objections?
>
Note for the archives: this has been removed as 417b80d.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | developer rohto | 2014-11-03 06:26:14 | 回复： Re: This may be a bug: odbc's function"check_client_encoding" have the same name with postgres's function. |
| Previous Message | Hiroshi Saito | 2014-10-30 12:50:04 | psqlODBC 09.03.0400 Released |