| From: | Enno Wein <ennowein(at)yahoo(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| 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:38:48 |
| Message-ID: | 33a6e05e-5dee-856e-d2a3-427eb190cc1e@yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I think you made that clear :-)
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.
On 3/16/18 07:31, Andrew Gierth wrote:
>>>>>> "Enno" == Enno Wein <ennowein(at)yahoo(dot)com> writes:
>
> Enno> This is an enhancement request to enable having tables which are
> Enno> both temporary and unlogged.
>
> ALL TEMPORARY TABLES ARE ALREADY UNLOGGED.
> ==========================================
>
> I don't know how to make this any clearer.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2018-03-16 14:56:17 | Re: BUG #15115: temporary AND unlogged tables for parallel db import |
| Previous Message | Sergei Kornilov | 2018-03-16 14:32:46 | Re: Missed pgq_coop and pgq_ext in actual pgdg repository |