Dave Cramer

@d6y can you test this the pgjdbc PR with slick ?

@d6y Thanks!

I would also like to see a date on the amendment at the very least.

@jolivaSan can you help me understand what you mean by "data base lock caused by the write operations" ?

HI @jolivaSan thanks for the explanation. As for explicit locking, it's pretty unusual for locks to actually block reads in Postgres, but the performance gains from splitting reads are pretty...

@maciejwalkowiak Interesting. Yes this would work, however I think that requires the application knows that it is requesting a read node or a write node. From what I can tell...

cool that makes a lot of sense.. thanks for the clarification

@hyunkshinft can you test the PR above ?

hmmm strange. I would think that should cause an exception to be thrown. FYI, there's no thread safety here. In reality you should not be closing it in another thread.

Something else must be going on. Any chance you can debug or provide a stand alone test case ?