Re: BUG #15115: temporary AND unlogged tables for parallel db import

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Enno Wein <ennowein(at)yahoo(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15115: temporary AND unlogged tables for parallel db import
Date: 2018-03-16 14:56:17
Message-ID: 87zi38gjrd.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>>>>> "Enno" == Enno Wein <ennowein(at)yahoo(dot)com> writes:

Enno> I think you made that clear :-)

Obviously not clear enough.

Enno> However, it doesn't seem to work like that. Even with ONLY either
Enno> unlogged (the global ones) and temprorary tables (the local ones), the
Enno> system still produces a huge amount of WAL/checkpoint writes.

So what you just said above is that you get a lot of WAL/checkpoint
writes when using unlogged non-temporary tables. What this implies is
that you have something _else_ going on, involving persistent tables
(i.e. non-temporary non-unlogged tables - these are the only kind that
get their data changes WAL-logged).

So please take this to a more appropriate forum where you can ask for
help in determining where your WAL or checkpoint traffic is coming from,
rather than wasting your time and ours in asking for a feature that
already exists and which from your own description above has nothing to
do with your problem.

--
Andrew.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephen Frost 2018-03-16 14:56:42 Re: BUG #15115: temporary AND unlogged tables for parallel db import
Previous Message Enno Wein 2018-03-16 14:38:48 Re: BUG #15115: temporary AND unlogged tables for parallel db import