From: | Paul Eggert <eggert(at)twinsun(dot)com> |
---|---|
To: | pgman(at)candle(dot)pha(dot)pa(dot)us |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: support for POSIX 1003.1-2001 hosts |
Date: | 2002-03-11 22:24:56 |
Message-ID: | 200203112224.g2BMOuc08619@shade.twinsun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
> From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
> Date: Mon, 11 Mar 2002 12:05:17 -0500 (EST)
>
> This is an interesting patch, but have not heard anyone else have this
> problem
That's not surprising, since I am purposely running a bleeding-edge
system to test PostgreSQL portability. Nobody is shipping POSIX
1003.1-2001 systems yet (the standard was only approved in December by
the IEEE, and it will not be an official ISO standard for a few more
weeks yet). But when they do, you will run into this problem.
> and am hesitant to add more cost to fix something that may not be
> broken. Sorry.
There is no cost to PostgreSQL in normal operation, since that part of
the source isn't affected at all. All that is affected is some of the
test scripts and documentation. I see little risk to incorporating
the patch, but of course it's your decision.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-03-11 22:44:26 | Re: psql: backslash fix |
Previous Message | Neil Conway | 2002-03-11 22:12:55 | Re: psql: backslash fix |