Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
pg_regress: could not set database default locales
I have just seen this failure on Windows - it appears to have nothing to
do there with finding an out of date libpq.
Actually, *any* failure in pg_regress's first atte
Andrew Dunstan <[EMAIL PROTECTED]> writes:
>>> pg_regress: could not set database default locales
> I have just seen this failure on Windows - it appears to have nothing to
> do there with finding an out of date libpq.
Actually, *any* failure in pg_regress's first attempt to invoke psql
yields t
Tom Lane wrote:
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
Try removing the "2>/dev/null" bit so that you can see if any error
messages come out from psql.
Ok, we have a detailed error now:
/home/pgsql80/pgsql/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/psql:
rel
On Mon, 2004-11-01 at 07:51, Tom Lane wrote:
> I looked at this a bit more and found that on Linux, the dynamic
> loader is documented to search "rpath" before LD_LIBRARY_PATH;
> so had we not specified an rpath when building the psql executable,
> pg_regress would have worked as intended. Sounds
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Oh, so you are using yesterday's libpq.so shared library ;-)
I am not sure there is any way around that except to go ahead and
install today's libpq. pg_regress can't do much more than set
LD_LIBRARY_PATH, and evide
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Oh, so you are using yesterday's libpq.so shared library ;-)
>>
>> I am not sure there is any way around that except to go ahead and
>> install today's libpq. pg_regress can't do much more than set
>> LD_LIBRARY_PATH, and evidently th
Tom Lane wrote:
> Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
> >> Try removing the "2>/dev/null" bit so that you can see if any error
> >> messages come out from psql.
>
> > Ok, we have a detailed error now:
>
> > /home/pgsql80/pgsql/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/psql:
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
>> Try removing the "2>/dev/null" bit so that you can see if any error
>> messages come out from psql.
> Ok, we have a detailed error now:
> /home/pgsql80/pgsql/src/test/regress/./tmp_check/install//usr/local/pgsql/bin/psql:
> relocation error:
> /home/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Sun, 31 Oct 2004, Tom Lane wrote:
LOG: unexpected EOF on client connection
Hmm, that seems to be the only sign of trouble, which I guess means we
have to conclude the problem is on the client side not the server side.
The part of the pg_regress
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
>>> pg_regress: could not set database default locales
>>
>> What shows up in the postmaster log file?
> You mean src/test/regress/log/postmaster.log, right?
> Actually not that much:
> LOG: unexpected EOF on client connection
Hmm, that seems to be the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Sun, 31 Oct 2004, Tom Lane wrote:
pg_regress: could not set database default locales
What shows up in the postmaster log file?
You mean src/test/regress/log/postmaster.log, right?
Actually not that much:
LOG: database system was shut down at 200
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
> pg_regress: could not set database default locales
What shows up in the postmaster log file?
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm getting this error on two different servers, one if them is the server
that I build PostgreSQL from CVS daily, the other one is a fresh one (used
to double-check the error)
Two servers have LANG="en_US.UTF-8". They are RHEL 3.0 Update 3 with
13 matches
Mail list logo
