| From: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, David Steele <david(at)pgmasters(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Subject: | Re: WIP: Covering + unique indexes. |
| Date: | 2017-03-30 19:27:06 |
| Message-ID: | 20170330192706.GA2565@e733.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Robert,
> Has anybody done some testing of this patch with the WAL consistency
> checker? Like, create some tables with indexes that have INCLUDE
> columns, set up a standby, enable consistency checking, pound the
> master, and see if the standby bails?
I've decided to run such a test. It looks like there is a bug indeed.
Steps to reproduce:
0. Apply a patch.
1. Build PostgreSQL using quick-build.sh [1]
2. Install master and replica using install.sh [2]
3. Download test.sql [3]
4. Run: `cat test.sql | psql`
5. In replica's logfile:
```
FATAL: inconsistent page found, rel 1663/16384/16396, forknum 0, blkno 1
```
> Has anybody tested this patch with amcheck? Does it break amcheck?
Amcheck doesn't complain.
[1] https://github.com/afiskon/pgscripts/blob/master/quick-build.sh
[2] https://github.com/afiskon/pgscripts/blob/master/install.sh
[3] http://afiskon.ru/s/88/93c544e6cf_test.sql
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-03-30 19:27:23 | Re: [COMMITTERS] pgsql: Default monitoring roles |
| Previous Message | Andres Freund | 2017-03-30 19:11:38 | Re: WIP: Covering + unique indexes. |