| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Enno Wein <ennowein(at)yahoo(dot)com> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, 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:42 |
| Message-ID: | 20180316145642.GI2416@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Greetings,
* Enno Wein (ennowein(at)yahoo(dot)com) wrote:
> However, it doesn't seem to work like that. Even with ONLY either
> unlogged (the global ones) and temprorary tables (the local ones), the
> system still produces a huge amount of WAL/checkpoint writes. In fact,
> the "wal-writer" and "checkpoint" processes are the biggest writers in
> the system. checkpoint process uses up to 9GB of Ram and wal produces
> more writes than any other process.
"Doesn't seem to work like that" really isn't enough to go on. If you'd
like for someone to look into this, posting a reproducible test case
which illustrates the bug you think you've found would be your best bet.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-16 15:25:03 | Re: BUG #15115: temporary AND unlogged tables for parallel db import |
| Previous Message | Andrew Gierth | 2018-03-16 14:56:17 | Re: BUG #15115: temporary AND unlogged tables for parallel db import |