| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WAL replay bugs |
| Date: | 2014-04-08 03:19:45 |
| Message-ID: | 53436AD1.8020607@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/07/2014 02:16 PM, Heikki Linnakangas wrote:
> I've been playing with a little hack that records a before and after
> image of every page modification that is WAL-logged, and writes the
> images to a file along with the LSN of the corresponding WAL record. I
> set up a master-standby replication with that hack in place in both
> servers, and ran the regression suite. Then I compared the after images
> after every WAL record, as written on master, and as replayed by the
> standby.
This is awesome ... thank you for doing this.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-04-08 03:29:03 | Default gin operator class of jsonb failing with index row size maximum reached |
| Previous Message | Tom Lane | 2014-04-08 01:47:38 | Re: Why is it not sane to pass ExecStoreTuple(shouldFree=true) for tuples point into buffers |