PostgreSQL 8.0.0rc2, 7.4.6
Solaris 9, FreeBSD 4.11-PRERELEASE
ECPG's CONNECT TO DEFAULT causes a segmentation fault. This
originally came up in the "Connection without database name" thread
in pgsql-hackers:
http://archives.postgresql.org/pgsql-hackers/2004-12/msg00813.php
Example:
#include
i
Theodore Petrosky <[EMAIL PROTECTED]> writes:
> I just found the time to try 8.0RC2 on OSX and I have
> a problem with 'make check'.
> Here is my configure..
> ./configure --disable-shared ...
--disable-shared breaks plpgsql, and probably a few other things. I'm
not exactly sure why we still ad
I just found the time to try 8.0RC2 on OSX and I have
a problem with 'make check'.
Here is my configure..
./configure --disable-shared --with-rendezvous
--enable-thread-safety
make then make check
== creating temporary installation
==
pg_regress: installation fa
Sankaranarayanan K V <[EMAIL PROTECTED]> writes:
> Is there any way by which I can impose the 32 char limit
> on the 8.0 database?
Rebuild with a different NAMEDATALEN.
> In which PGSQL release did the table name length limitation change?
RTF release notes.
regards, tom
Configurations:
A: PostgreSQL 7.2.2 on a RedHat Linux 6.2
B: Windows PostgreSQL 8.0.0 RC2
(A) truncates table names with length >32 characters
to 32 characters.
I have some legacy application which relies on this fact.
This code uses 32+ chars for creating the schema but
uses 32- chars for que