Repository navigation
Zero Copy #1
Description
A connection-to-connection COPY management object which provides efficient transmission of COPY data.
This object will use a mutable buffer in conjunction with a function that will identify the current COPY state. Multiple target connections will need to be supported. Exceptions thrown by this object's main method will need to be generalized into a exception identifying the target that caused the failure. This will be one component in order to allow the user to craft fault tolerance capabilities. The next component is the ability to dynamically remove a target from the copy manager. This will allow the COPY to continue after the fault was identified as an acceptable risk.
Activity
jwp commentedon Mar 1, 2010
This has a couple stages. The initialization stage is tricky. It involves getting the connection into a COPY state by executing a statement and causing it to jump out early.
The primary stage is less tricky as it mostly involves noting the state and when the COPY is over.
jwp commentedon Mar 1, 2010
What kind of information should the state analyzer provide? So far, number of total messages in data, and bytes remaining in the last message. If there is no complete message, then number of messages in data is zeor.
jwp commentedon Mar 17, 2010
This is almost done. Currently, the only hang-up is some error control edge cases during exit.
jwp commentedon Mar 26, 2010
This is done in v1.0.