| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <heikki(dot)linnakangas(at)enterprisedb(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: default_isolation_level='serializable' crashes on Windows |
| Date: | 2012-08-24 02:57:41 |
| Message-ID: | 5036A7550200002500049ABA@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Tom Lane wrote:
> "Kevin Grittner" writes:
>> I'll run through my tests again tonight, against your patch, not
>> that I expect any problems with it. Unfortunately I can't test
>> Windows, as I don't have a build environment for that.
>
> FWIW, you can approximate Windows close enough for this type of
> problem by building with EXEC_BACKEND defined. I usually add the
> #define to pg_config.h after configuring, though of course there's
> more than one way to do it.
It tested out fine both ways.
For anybody else wanting to use EXEC_BACKEND for testing -- don't
count on --enable-depend to rebuild everything correctly. I used
maintainer-clean and it worked.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-08-24 03:15:06 | Re: Why does analyze_new_cluster.sh use sleep? |
| Previous Message | Craig Ringer | 2012-08-24 01:47:10 | Recently noticed documentation issues |