Re: Commit(?) overhead

2019-04-09 Thread Andres Freund
Hi, On 2019-04-09 17:12:27 -0500, Justin Pryzby wrote: > You could test that's the issue by comparing with fsync=off (please read what > that means and don't run your production cluster like that). > https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-FSYNC I suggest testing it wi

Re: Commit(?) overhead

2019-04-09 Thread Justin Pryzby
On Wed, Apr 10, 2019 at 09:26:22AM +1200, Duncan Kinnear wrote: > - On 5 Apr, 2019, at 4:14 AM, Jeff Janes wrote: > > > On Thu, Apr 4, 2019 at 3:42 AM Duncan Kinnear > > wrote: > > >> the EXPLAIN (ANALYSE, TIMING TRUE) of this query gives: > > >> Update on next_id (cost=0.14..8.16 rows=1

Re: Commit(?) overhead

2019-04-09 Thread Duncan Kinnear
- On 5 Apr, 2019, at 4:14 AM, Jeff Janes wrote: > On Thu, Apr 4, 2019 at 3:42 AM Duncan Kinnear < [ > mailto:duncan.kinn...@mccarthy.co.nz | duncan.kinn...@mccarthy.co.nz ] > > wrote: >> the EXPLAIN (ANALYSE, TIMING TRUE) of this query gives: >> Update on next_id (cost=0.14..8.16 rows=1 w