On Thu, Mar 3, 2016 at 12:47 AM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Well, the CopyData message has an Int32 field for the message length. > I don't know the FE/BE protocol very well but I suppose each row > corresponds to one CopyData message, or perhaps each column corresponds > to one CopyData message. In either case, it's not possible to go beyond > 2GB without changing the protocol ...
Based on what I know from this stuff (OOM libpq and other stuff remnants), one 'd' message means one row. fe-protocol3.c and CopySendEndOfRow in backend's copy.c are confirming that as well. I am indeed afraid that having extra logic to get chunks of data will require extending the protocol with a new message type for this purpose. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
