From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Scott Ribe <scott_ribe(at)killerbytes(dot)com>, Bill Moran <wmoran(at)collaborativefusion(dot)com>, "pgsql-general postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Small request re error message |
Date: | 2007-02-19 12:33:43 |
Message-ID: | 20070219123343.GR9724@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bruce Momjian wrote:
> Scott Ribe wrote:
> > > Oh. Yea, I can see that, but even if the endian-ness is the same, it
> > > still might not work. Even a different compiler flag will cause a
> > > failure to run properly.
> >
> > Sure. You can't flag every possible error. But my Intel & PPC Macs look
> > identical, and I compile with identical flags. So it would help people like
> > me, all one or two of us ;-)
>
> What would make more sense than printing the hex is to print a specific
> message if the endian-ness doesn't match, but I am worried people might
> assume it will work when the endian does match.
That doesn't make much sense because we give different error messages,
each telling that one little check failed.
I think adding the hex code is not helpful in the general case, but
maybe we could check for endianness if the control version fails, and
add that info in a HINT or something.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Leonel Nunez | 2007-02-19 12:38:00 | Re: Postgresql 8.1 y Debian [ Era: Re: postgreSQL ] |
Previous Message | Alvaro Herrera | 2007-02-19 12:30:20 | Re: QNX, RTOS y Postgres |