We use autoconf for configure. I like the idea of using the thread-safe
crypt if available, though it does confuse things because it makes
thread-safeness contingent of SSL being installed. I question whether
it is just easier to say it isn't thread-safe because I am not sure how
someone is goi
[EMAIL PROTECTED] writes:
> collation fails sorting because of strcoll() bug
Sorry, strcoll() is behaving as defined. If you don't like it, use
a different LOCALE. Or at the very least, complain to the strcoll
authors, not us ;-)
regards, tom lane
-
Mathias August Gruber (mgruber) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
collation fails sorting because of strcoll() bug
Long Description
Hi there,
I was trying to migrate a MS-SQL Server database to a Postgresql platform about two
years
Vladimir ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
CREATE TABLE with implicit index should not fail if index already exists
Long Description
When PostgreSQL tries to create implicit index during table creation and assumed
=?iso-8859-1?q?Laurent=20FAILLIE?= <[EMAIL PROTECTED]> writes:
>> The easiest way to get back to a working database is
>> to UPDATE the
>> pg_language row with the correct OID of the call
>> handler function.
> Hum, so I may try
> update pg_language set lanplcallfoid=374578 where
> lanname='plpg
On 6 Mar 2002, Arkadiusz Miskiewicz wrote:
>
> Hi,
>
> I'm building postgresql 7.2 on power pc linux using:
> gcc-2.95.4-0.20010823.3
> glibc-2.2.5-2
> binutils-2.11.90.0.19-4
>
> [builder@pld_ppc regress]$ cat /proc/cpuinfo
> cpu : 740/750
> temperature : 45 C (uncalibrated)
> c
=?iso-8859-1?q?Laurent=20FAILLIE?= <[EMAIL PROTECTED]> writes:
> scheduling=# select * from pg_proc where
> proname='plpgsql_call_handler';
>proname| proowner | prolang | proisinh
> | proistrusted | proiscachable | proisstrict |
> pronargs | proretset | prorettype | proargtypes |
This time I've included the log file...
su-2.02$ cat postmaster.log
DEBUG: database system was shut down at 2002-03-03 19:43:39 EST
DEBUG: checkpoint record is at 0/109664
DEBUG: redo record is at 0/109664; undo record is at 0/0; shutdown TRUE
DEBUG: next transaction id: 89; next oid: 16556
D
Hi,
I'm building postgresql 7.2 on power pc linux using:
gcc-2.95.4-0.20010823.3
glibc-2.2.5-2
binutils-2.11.90.0.19-4
[builder@pld_ppc regress]$ cat /proc/cpuinfo
cpu : 740/750
temperature : 45 C (uncalibrated)
clock : 333MHz
revision: 2.2 (pvr 0008 0202)
bog
Hi All,
I've just compiled and checked version 7.2 of the system on BSDI 4.0 and
have noticed the following errors in the regression.diffs file
! psql: PQconnectPoll() -- couldn't send startup packet: errno=32
! Broken pipe
This is occurring for almost all of the test. Does anyone have any ide
10 matches
Mail list logo