On 9/14/10 12:15 PM, David Shrewsbury wrote:
> #2 does not suffer from the concurrency issue of #1, but it does
> mean marginally more work for TransactionApplier implementers
> to buffer GBP messages until the end Transaction message is
> read.
How does the receiver know how many messages are coming in that
transaction? That is, how will it know when it's done receiving the
bulk load and can proceed? And is there any possibility of the bulk
load messages arriving out of order?
*Not* that this is a vote for (1), an approach which seems broken by
design. Put the load on the receivers, where it belongs.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
