Simon Riggs wrote: > The interesting point is you can have a huge data grinding app, yet with > other tables alongside that hold more important data. In that scenario, > 90% of the data would be COMMIT NOWAIT, whilst the small important data > is safe.
Does this means that the regular COMMIT is slower because it has to force more data to disk? I imagine that this isn't the case, because it's not the write itself that's slow; rather, it's the wait until the fsync on WAL is reported complete. However, did you measure this? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
