On Jul 15, 2015, at 8:35 PM, Curtis Maloney <cur...@acommoncreative.com> wrote:
> On 16 July 2015 at 05:01, Shai Berger <s...@platonix.com> wrote: >> This is a shot in the dark: Could it be that rolling back transactions >> involving unlogged tables is harder? The idea does make sense, and running >> the >> test suite does an extremely untypical amount of rollbacks. > > I thought at some point I read that unlogged tables didn't support > transactions... however, the docs don't agree. Transactions behave the same in PostgreSQL for both logged and unlogged tables (except for, of course, the lack of a commit / rollback entry in the WAL), and there's no appreciable performance benefit on COMMIT and ROLLBACK time for logged vs unlogged. My guess is that the Django tests are not generating enough data to make the WAL activity be a significant time sink. By the way, I would strongly advise *against* *ever* even mentioning fsync = off anywhere in the Django documentation; that is such a horribly bad idea in 99.95% of real-life situations that steering people towards it as a "go faster" button is very unwise. -- -- Christophe Pettus x...@thebuild.com -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9B2A4A22-09FF-4634-AF4A-536C022FC57E%40thebuild.com. For more options, visit https://groups.google.com/d/optout.
