| From: | Amul Sul <sulamul(at)gmail(dot)com> |
|---|---|
| To: | "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-09-29 09:40:24 |
| Message-ID: | CAAJ_b95aUBD2JC8rBHadLx65qNj+Mf13DscJ--53Wvcs9QwAhQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 29, 2020 at 1:58 PM tsunakawa(dot)takay(at)fujitsu(dot)com
<tsunakawa(dot)takay(at)fujitsu(dot)com> wrote:
>
> Hello,
>
>
> We'd like to propose a feature to disable WAL to speed up data loading. This was inspired by a feature added in the latest MySQL. I wish you won't fear this feature...
>
TWIMW, pg_bulkload contrib module[1], also does the same for the
faster data loading.
Regards,
Amul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-09-29 09:43:13 | Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers |
| Previous Message | David Rowley | 2020-09-29 09:26:06 | Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path |