| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)cc>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: strange buildfarm failure on lionfish |
| Date: | 2007-07-25 21:51:28 |
| Message-ID: | 5103.1185400288@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> On Wed, 2007-07-25 at 22:20 +0100, Gregory Stark wrote:
>> Also, it might let us set up a standby database in the regression
>> suite which would give us some xlog coverage as well which is a
>> critical portion of the system the regression suite doesn't test at
>> all.
> I like that general thought and will help where I can.
One pretty crude test I use a lot is to "kill -9" the bgwriter or some
other subprocess immediately after the regression tests finish.
Assuming you have checkpoints far enough apart, this forces a replay
from WAL of the entire regression sequence. Doesn't exercise archiving
though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-07-26 00:04:56 | FileUnlink is broken, but it's dead code anyway |
| Previous Message | Tom Lane | 2007-07-25 21:46:27 | Re: Machine available for community use |