| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com>, 'Ashutosh Bapat' <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Disable WAL logging to speed up data loading |
| Date: | 2020-10-01 01:01:56 |
| Message-ID: | 81ec3320-b43f-affd-5681-56be65bcce5f@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020/09/30 12:10, osumi(dot)takamichi(at)fujitsu(dot)com wrote:
> Hello, Ashutosh
>
>> Can they use a database with all unlogged tables?
> Unfortunately, no. They want to switch a cluster condition to "without WAL logging"
> only when they execute night bulk loading for their data warehouse.
> In other words, they would like to keep their other usual operations with WAL.
> In addition, using all tables as unlogged brings about
> the risk to lose data warehouse's data caused by an unexpected server crash or power outage.
But the same issue can happen even in the proposed approach
because Tsunakawa-san explains as follows?
> The server refuses to start (pg_ctl start fails) after an abnormal shutdown due to power outage, pg_ctl's immediate shutdown, etc, showing a straightforward message like MySQL.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2020-10-01 01:23:50 | Re: New statistics for tuning WAL buffer size |
| Previous Message | Tom Lane | 2020-10-01 00:40:58 | Re: BUG #16419: wrong parsing BC year in to_date() function |