Re: BUG #15115: temporary AND unlogged tables for parallel db import - Mailing list pgsql-bugs

From Andrew Gierth
Subject Re: BUG #15115: temporary AND unlogged tables for parallel db import
Date
Msg-id 87zi38gjrd.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: BUG #15115: temporary AND unlogged tables for parallel db import  (Enno Wein <ennowein@yahoo.com>)
Responses Re: BUG #15115: temporary AND unlogged tables for parallel db import  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
>>>>> "Enno" == Enno Wein <ennowein@yahoo.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.


pgsql-bugs by date:

Previous
From: Enno Wein
Date:
Subject: Re: BUG #15115: temporary AND unlogged tables for parallel db import
Next
From: Stephen Frost
Date:
Subject: Re: BUG #15115: temporary AND unlogged tables for parallel db import