| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: What exactly is our CRC algorithm? |
| Date: | 2014-12-26 18:11:43 |
| Message-ID: | 20141226181141.GD3763@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 26, 2014 at 04:52:58PM +0100, Andres Freund wrote:
> >Uh, what if the system is compiled on a different CPU that it
> >is
> >run on? Seems we would need a run-time CPU test.
>
> That's the cpuid thing mentioned above.
Is this something that could potentially change the data stored on disk?
Does pg_upgrade need to check for changes in this area? Is the
detection exposed by pg_controldata? Could this affect running the data
directory on a different CPU?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhijit Menon-Sen | 2014-12-26 18:22:41 | Re: What exactly is our CRC algorithm? |
| Previous Message | Tom Lane | 2014-12-26 17:59:52 | Re: Some other odd buildfarm failures |