dear pgsql-bugs
i'm running postgresql 7.1.2 on freebsd4.3 my
application consists of several components running on win32s clients some of the
modules interact with each other on the network using udp and tcp packets i have
nearly 14 clients running on the server i mentioned before on a workg
The server is running:
PostgreSQL version 7.0.2
RedHat Linux 6.2
When using ORDER BY in an SQL statement where the data type is varchar and
the data are unix directory paths, the forward slashes (/) are ignored,
causing the results to be returned in the incorrect order.
Example:
Here is the
I tried linking both plperl.so and libperl.so in /usr/lib and
/usr/shlib, setting my LD_LIBRARY_PATH environment variable to include
those directories, recompiling the source for Pl/Perl, and still get the
same message. Unfortunately, Tru64 4.0F doesn't have an equivalent of
the ldd command that I
Hi everyone!
While having problems with large objects I discovered
a faulty implementation of the 'rw' parameter for
pg_lo_open.
in the file
src/interfaces/libpgtcl/pgtclCmds.c
the second letter of this parameter is incorporated
into the mode variable by _ANDING_ another value
(INV_READ / I
Kristian Lance <[EMAIL PROTECTED]> writes:
> Note that the program appears to make no distinction between /x/c and
> /xc.
Sounds like you're running in en_US locale. You might prefer to use
plain C locale.
regards, tom lane
---(end of broadcast)
On Thu, 29 Nov 2001, Kristian Lance wrote:
> The server is running:
>
> PostgreSQL version 7.0.2
> RedHat Linux 6.2
>
> When using ORDER BY in an SQL statement where the data type is varchar and
> the data are unix directory paths, the forward slashes (/) are ignored,
> causing the results to be
Thanks for your help. The main problem that was holding me up was that I
wasn't sure what the equivalent of ldd was on Tru64 4.0F (ldd is
available on version 4.0G and higher). I found out odump -Dl
libraryname.so is the closest equivalent on this OS. From that, I
discovered the missing library wa
Paul Smith ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
UPDATE fails after an index is changed
Long Description
I had to drop and re-create an index on a table for a large insert. Then I needed to
run an UPDATE on a differe
[EMAIL PROTECTED] writes:
> I had to drop and re-create an index on a table for a large insert. Then I needed to
>run an UPDATE on a different table that gets its values from the first table. UPDATE
>fails with this error message:
> 'ERROR: Index 6708054 does not exist'.
What do you mean by "
Mike Smialek wrote:
>
> Configuration:
> Windows 2000 Server
> cygwin 2.78.2.9
> PostgreSQL 7.1.3
> psqlODBC 7.1.8
> pgAdmin II 1.1.66
>
> Bug:
> Capital letters cannot be used in column names used in foreign key
> constraints
>
> All Smalls succeeds:
[snip]
> C
Configuration:
Windows 2000 Server
cygwin 2.78.2.9
PostgreSQL 7.1.3
psqlODBC 7.1.8
pgAdmin II 1.1.66
Bug:
Capital letters cannot be used in column names used in foreign key
constraints
All Smalls succeeds:
-- Table: significance
CREATE TABLE "signific
11 matches
Mail list logo