|
1 | | -<!-- $Header: /cvsroot/pgsql/doc/src/sgml/regress.sgml,v 1.29 2002/10/12 16:31:55 petere Exp $ --> |
| 1 | +<!-- $Header: /cvsroot/pgsql/doc/src/sgml/regress.sgml,v 1.30 2002/11/08 20:26:12 tgl Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="regress"> |
4 | 4 | <title id="regress-title">Regression Tests</title> |
@@ -264,47 +264,26 @@ PGTZ='PST8PDT7,M04.01.0,M10.05.03'; export PGTZ |
264 | 264 | Some of the tests involve computing 64-bit (<type>double |
265 | 265 | precision</type>) numbers from table columns. Differences in |
266 | 266 | results involving mathematical functions of <type>double |
267 | | - precision</type> columns have been observed. The float8 and |
268 | | - geometry tests are particularly prone to small differences across |
269 | | - platforms, or even with different compiler optimization options. |
| 267 | + precision</type> columns have been observed. The<literal>float8</> and |
| 268 | +<literal>geometry</> tests are particularly prone to small differences |
| 269 | +acrossplatforms, or even with different compiler optimization options. |
270 | 270 | Human eyeball comparison is needed to determine the real |
271 | 271 | significance of these differences which are usually 10 places to |
272 | 272 | the right of the decimal point. |
273 | 273 | </para> |
274 | 274 |
|
| 275 | + <para> |
| 276 | + Some systems display minus zero as <literal>-0</>, while others |
| 277 | + just show <literal>0</>. |
| 278 | + </para> |
| 279 | + |
275 | 280 | <para> |
276 | 281 | Some systems signal errors from <function>pow()</function> and |
277 | 282 | <function>exp()</function> differently from the mechanism |
278 | 283 | expected by the current <productname>PostgreSQL</productname> |
279 | 284 | code. |
280 | 285 | </para> |
281 | 286 | </sect2> |
282 | | - |
283 | | - <sect2> |
284 | | - <title>Polygon differences</title> |
285 | | - |
286 | | - <para> |
287 | | - Several of the tests involve operations on geographic data about |
288 | | - the Oakland/Berkeley, California street map. The map data is expressed as |
289 | | - polygons whose vertices are represented as pairs of <type>double |
290 | | - precision</type> numbers (decimal latitude and |
291 | | - longitude). Initially, some tables are created and loaded with |
292 | | - geographic data, then some views are created that join two |
293 | | - tables using the polygon intersection operator |
294 | | - (<literal>##</literal>), then a select is done on the view. |
295 | | - </para> |
296 | | - |
297 | | - <para> |
298 | | - When comparing the results from different platforms, differences |
299 | | - occur in the 2nd or 3rd place to the right of the decimal |
300 | | - point. The SQL statements where these problems occur are the |
301 | | - following: |
302 | | -<programlisting> |
303 | | -SELECT * from street; |
304 | | -SELECT * from iexit; |
305 | | -</programlisting> |
306 | | - </para> |
307 | | - </sect2> |
308 | 287 |
|
309 | 288 | <sect2> |
310 | 289 | <title>Row ordering differences</title> |
|