| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org>,<rhaas(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Adjust OLDSERXID_MAX_PAGE based on BLCKSZ. |
| Date: | 2011-07-08 15:16:53 |
| Message-ID: | 4E16D915020000250003F102@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> So, what are the consequences if a compiler allows the expression
> to overflow to zero? Does this mean that beta3 is dangerously
> broken?
The risk to anyone not using serializable transactions is most
definitely zero. I've been running with this patch in my daily
tests (including the isolation tests and `make installcheck-world`
with default_transaction_isolation = 'serializable' without seeing
any problems. The best way to check would be to run the isolation
tests on a platform reporting the overflow.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-07-08 15:32:47 | Re: Re: [COMMITTERS] pgsql: Adjust OLDSERXID_MAX_PAGE based on BLCKSZ. |
| Previous Message | Stuart Bishop | 2011-07-08 15:13:17 | Re: storing TZ along timestamps |