Re: Streaming replication and non-blocking I/O
От | Fujii Masao |
---|---|
Тема | Re: Streaming replication and non-blocking I/O |
Дата | |
Msg-id | 3f0b79eb0912151928w4002a79cu9616d310ab76dd93@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Streaming replication and non-blocking I/O (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: Streaming replication and non-blocking I/O
|
Список | pgsql-hackers |
On Tue, Dec 15, 2009 at 3:47 AM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > Tom Lane wrote: >> The very, very large practical problem with this is that if you decide >> to change the behavior at any time, the only way to be sure that the WAL >> receiver is using the right libpq version is to perform a soname major >> version bump. The transformations done by libpq will essentially become >> part of its ABI, and not a very visible part at that. > > Not having to change the libpq API would certainly be a big advantage. Done; I replaced PQgetXLogData and PQputXLogRecPtr with PQgetCopyData and PQputCopyData. git://git.postgresql.org/git/users/fujii/postgres.gitbranch: replication Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: