Re: Libpq PGRES_COPY_BOTH - version compatibility
От | Robert Haas |
---|---|
Тема | Re: Libpq PGRES_COPY_BOTH - version compatibility |
Дата | |
Msg-id | AANLkTi=ubLirJrEdwCs4Y0Za6BbzbmrNeDLNyewo0dLe@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Libpq PGRES_COPY_BOTH - version compatibility (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: Libpq PGRES_COPY_BOTH - version compatibility
Re: Libpq PGRES_COPY_BOTH - version compatibility |
Список | pgsql-hackers |
On Mon, Jan 3, 2011 at 6:55 AM, Magnus Hagander <magnus@hagander.net> wrote: >> ISTM that the correct fix is to increment to protocol version number to >> 3.1 and send PGRES_COPY_OUT if the client requests version 3.0. That's >> what the version numbers are for, no? > > In a way - yes. I assume we didn't do that because it's considered "internal". > > It still won't help in my situation though - I need to know what > version of the libpq headers I have in order to even be able to > *compile* the program. At runtime, I could check against the server > version, and get around it. This is listed on the open items list as "raise protocol version number", but the above discussion suggests both that this might be unnecessary and that it might not solve Magnus's problem anyway. What do we want to do here? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: