Re: Transactions and paged_each

2016-09-02 Thread Trevor Turk
On Friday, September 2, 2016 at 2:31:29 PM UTC-5, Jeremy Evans wrote: > > I'm guessing streaming would preform better, but you would still need to > use a separate thread or sharding when using streaming. > That's great. I'll give streaming a try, but I believe the bottleneck isn't going to be

Re: Transactions and paged_each

2016-09-02 Thread Jeremy Evans
On Friday, September 2, 2016 at 11:48:46 AM UTC-7, Trevor Turk wrote: > On Friday, September 2, 2016 at 1:19:02 PM UTC-5, Jeremy Evans wrote: >> >> To work around this issue, you can use sharding (Dataset option like >> :servers=>{:foo=>{}}), and do dataset.server(:foo).paged_each. >> Alternati

Re: Transactions and paged_each

2016-09-02 Thread Trevor Turk
On Friday, September 2, 2016 at 1:19:02 PM UTC-5, Jeremy Evans wrote: > > To work around this issue, you can use sharding (Dataset option like > :servers=>{:foo=>{}}), and do dataset.server(:foo).paged_each. > Alternatively, you can issue queries in a separate thread inside the > Dataset#each b

Re: Transactions and paged_each

2016-09-02 Thread Jeremy Evans
On Friday, September 2, 2016 at 10:43:50 AM UTC-7, Trevor Turk wrote: > > Hello -- just reporting back on my progress so far. > > It appears we can use paged_each safely, however I was surprised to find > that we can't run two simultaneously if they issue updates in the block. > In general it's

Re: Transactions and paged_each

2016-09-02 Thread Trevor Turk
On Thursday, September 1, 2016 at 12:51:58 PM UTC-5, Jeremy Evans wrote: > > On Thursday, September 1, 2016 at 9:42:11 AM UTC-7, Trevor Turk wrote: >> >> On Thursday, September 1, 2016 at 11:34:44 AM UTC-5, Trevor Turk wrote: >>> >>> In my case, I'm on AWS RDS PostgreSQL version 9.3.10 and I'm usin