On Feb 17, 2017, at 4:05 PM, Jeff Janes wrote:
> It will probably be easier to refactor the code than to quantify just how
> much damage it does.
Thanks for all the info. It looks like this is something worth prioritizing
because of the effects on indexes.
We had discussed a fix and pointed
On Thu, Feb 16, 2017 at 11:33 AM, 2xlp - ListSubscriptions <
postg...@2xlp.com> wrote:
> Can someone enlighten me to how postgres handles disk writing? I've read
> some generic remarks about buffers, but that's about it.
>
> We have a chunk of code that calls Postgres in a less-than-optimal way
On 02/16/2017 11:33 AM, 2xlp - ListSubscriptions wrote:
Can someone enlighten me to how postgres handles disk writing? I've read some
generic remarks about buffers, but that's about it.
We have a chunk of code that calls Postgres in a less-than-optimal way within a
transaction block. I'm
Can someone enlighten me to how postgres handles disk writing? I've read some
generic remarks about buffers, but that's about it.
We have a chunk of code that calls Postgres in a less-than-optimal way within a
transaction block. I'm wondering where to prioritize fixing it, as the traffic
on
