From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | 2xlp - ListSubscriptions <postgres(at)2xlp(dot)com>, pgsql-general general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: disk writes within a transaction |
Date: | 2017-02-16 20:10:08 |
Message-ID: | d5299a16-7022-c4e0-a1d1-da2418f2333a@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 wondering where to prioritize fixing it, as the traffic on the wire isn't an issue.
>
> Basically the code looks like this:
>
> begin;
> update foo set foo.a='1' where foo.bar = 1;
> ...
> update foo set foo.b='2' where foo.bar = 1;
> ...
> update foo set foo.c='3' where foo.bar = 1;
> commit;
>
> If the updates are likely to be a memory based operation, consolidating them can wait. If they are likely to hit the disk, I should schedule refactoring this code sooner than later.
I would suggest taking a look at:
https://www.postgresql.org/docs/9.6/static/wal-configuration.html
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | David Hinkle | 2017-02-16 20:22:29 | Re: Bad planning data resulting in OOM killing of postgres |
Previous Message | 2xlp - ListSubscriptions | 2017-02-16 19:33:13 | disk writes within a transaction |