| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com> |
| Cc: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Implement UNLOGGED clause for COPY FROM |
| Date: | 2020-08-26 10:50:49 |
| Message-ID: | CAA4eK1+SaXD+cHDPCaJTkcEWjjD41W_vZgVNKzfbB2SX_qQsTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 26, 2020 at 12:54 PM tsunakawa(dot)takay(at)fujitsu(dot)com
<tsunakawa(dot)takay(at)fujitsu(dot)com> wrote:
>
>
> Following this idea, what do you think about adding a new value "none" to wal_level, where no WAL is generated? The setting of wal_level is recorded in pg_control. The startup process can see the value and reject recovery after abnormal shutdown, emitting a message similar to MySQL's.
>
So you want your users to shutdown and restart the server before Copy
because that would be required if you want to change the wal_level.
However, even if we do that, users who are running the server
previously with wal_level as 'replica' won't be happy after doing this
change. Because if they change the wal_level to 'none' for certain
operations like bulk load and then again change back the mode to
'replica' they need to back up the database again to setup 'replica'
as they can't continue replication from the previous point (consider
update on a page for which previously WAL was not written).
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-08-26 11:00:57 | Re: Allow CURRENT_ROLE in GRANTED BY |
| Previous Message | Kyotaro Horiguchi | 2020-08-26 09:13:23 | Re: "cert" + clientcert=verify-ca in pg_hba.conf? |