On Thu, May 24, 2012 at 4:52 AM, Magnus Hagander <mag...@hagander.net> wrote: > On Wed, May 23, 2012 at 8:11 PM, Fujii Masao <masao.fu...@gmail.com> wrote: >> On Tue, May 22, 2012 at 11:04 PM, Robert Haas <robertmh...@gmail.com> wrote: >>> On Mon, May 14, 2012 at 2:24 PM, Fujii Masao <masao.fu...@gmail.com> wrote: >>>> On Fri, May 11, 2012 at 11:43 PM, Magnus Hagander <mag...@hagander.net> >>>> wrote: >>>>> Should we go down the easy way and just reject connections when the flag >>>>> is >>>>> mismatching between the client and the server (trivial to do - see the >>>>> attached patch)? >>>> >>>> + char *tmpparam; >>>> >>>> You forgot to add "const" before "char", which causes a compile-time >>>> warning. >>> >>> I went ahead and committed this, with this fix and a slight change to >>> the message text. >> >> Thanks! >> >>> Hope that's OK with everyone... >> >> What about calling PQfinish() before exit() to avoid "unexpected EOF >> connection" error? >> Patch attached. > > Makes sense, applied.
Thanks! So, let's go back to the original problem: pg_receivexlog still doesn't work fine under --disable-integer-datetimes. I previously posted the patch which fixes that problem. http://archives.postgresql.org/message-id/CAHGQGwFutqnFPBYcHUCuoy1zMVDXto=o4ogsjrbwxw4zj2t...@mail.gmail.com Attached is the updated version of the patch. Comments? Regards, -- Fujii Masao
timeout_handling_v3.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
