| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Matt Kelly <mkellycs(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
| Subject: | Re: amcheck (B-Tree integrity checking tool) |
| Date: | 2016-03-13 20:22:54 |
| Message-ID: | CAM3SWZRpS8PEchWcEQD6eLSVGFS4vF5-7XPn2xQSf4kPL=FzrQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Mar 12, 2016 at 7:46 PM, Matt Kelly <mkellycs(at)gmail(dot)com> wrote:
> You can actually pretty easily produce a test case by setting up streaming
> replication between servers running two different version of glibc.
>
> I actually wrote a tool that spins up a pair of VMs using vagrant and then
> sets them up as streaming replica's using ansible. It provides a nice one
> liner to get a streaming replica test environment going and it will easily
> provide the cross glibc test case. Technically, though it belongs to Trip
> because I wrote it on company time. Let me see if I can open source a
> version of it later this week that way you can use it for testing.
That could be interesting. The earlier prototypes of this tool are
known to have detected glibc collation incompatibilities in real
production systems.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-03-13 20:24:46 | Re: memory leak in GIN |
| Previous Message | Jim Nasby | 2016-03-13 19:52:03 | Re: Sanity checking for ./configure options? |