Re: Disable WAL logging to speed up data loading - Mailing list pgsql-hackers

From movead li
Subject Re: Disable WAL logging to speed up data loading
Date
Msg-id 161050957776.8805.3848120545514562434.pgcf@coridan.postgresql.org
Whole thread Raw
In response to Re: Disable WAL logging to speed up data loading  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses RE: Disable WAL logging to speed up data loading  ("osumi.takamichi@fujitsu.com" <osumi.takamichi@fujitsu.com>)
List pgsql-hackers
I read the patch and have two points:

1. I do basebackup for database then switch wal level from logical to none to logical and
of cause I archive the wal segments. Next I do PITR base on the basebackup, as a result
it success startup with a waring said maybe data missed.

Because the 'none' level is to bulkload data, do you think it's good that we still support
recover from a 'none' wal level.

2. I just mark wal_level as 'none' but fail to startup, it success after I drop the publication and
it's subscription,mark max_wal_senders as 0, drop replicate slot. I think it worth to write how 
we can startup a 'none' wal level database in document .

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Logical decoding without slots: decoding in lockstep with recovery
Next
From: "kuroda.hayato@fujitsu.com"
Date:
Subject: RE: Terminate the idle sessions