| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Buildfarm feature request: some way to track/classify failures |
| Date: | 2007-03-19 13:04:03 |
| Message-ID: | 87hcshjsfw.fsf@stark.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Also, for completeness, the causes I wrote off as not interesting
> (anymore, in some cases):
>
> missing BYTE_ORDER definition for Solaris | 2007-01-10 14:18:23 | 1
What is this BYTE_ORDER macro? Should I be using it instead of the
AC_C_BIGENDIAN test in configure for the packed varlena patch?
> row-ordering discrepancy in rowtypes test | 2007-02-10 03:00:02 | 3
Is this because the test is fixed or unfixable? If not shouldn't the test get
an ORDER BY clause so that it will reliably pass on future versions?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-03-19 13:11:15 | Re: Indexam interface proposal |
| Previous Message | Martijn van Oosterhout | 2007-03-19 12:59:46 | Re: Indexam interface proposal |