| From: | "Brad Nicholson" <bradn(at)ca(dot)ibm(dot)com> |
|---|---|
| To: | Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Re: Enabling checksums on a streaming replica |
| Date: | 2019-06-26 18:08:19 |
| Message-ID: | OF0F1A53A2.637681AC-ON85258425.00636ACB-85258425.0063A36D@notes.na.collabserv.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru> wrote on 06/26/2019 12:37:10 PM:
> From: Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru>
> To: pgsql-general(at)lists(dot)postgresql(dot)org
> Date: 06/26/2019 12:37 PM
> Subject: [EXTERNAL] Re: Enabling checksums on a streaming replica
>
> Hello!
> Very interesting idea, but what about full page writes, that comes
> from master?
> Can they be a problem?
In testing, it doesn't appear to matter. I've ensured that I've generated
some full page writes (confirmed via pg_waldump), and those apply fine.
The one thing I'm not sure of, when verifying checksums via pg_checksums I
see blocks being skipped. I'm not sure what or why it is skipping blocks,
and if that indicates a problem or not.
pg_checksums -c /data/10_repl/
Checksum scan completed
Files scanned: 1530
Blocks scanned: 100782
Blocks skipped: 3
Bad checksums: 0
Data checksum version: 1
Brad
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Enrico Pirozzi | 2019-06-27 07:49:18 | Re: migrating from Oracle to PostgreSQL 11 |
| Previous Message | Grigory Smolkin | 2019-06-26 16:37:10 | Re: Enabling checksums on a streaming replica |