[ Slightly edited take #2: I wasn't subscribed (again :-() to the
-bugs list. Moderator -- you can kill any postings of mine in the
queue, if you care to. :-]
Hi,
Today I built postgresql-7.1beta6 on NetBSD-1.4.2/i386, which uses
a.out binary format. (NetBSD 1.5/i386 uses ELF.)
I found th
[ I sent a similar message with less information to -bugs earlier, and
it got held for moderation. The moderator might like to kill that
one ... ]
Hi,
PostgreSQL 7.1beta6 built on NetBSD-1.5/i386 fails the polygon test in
'make check'. The following change to resultmap makes all tests
(oth
Robert Bihlmeyer ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
deferred constraints don't work correctly
Long Description
Using the example code, I get "ERROR: referential integrity violation - key
in foo still referenced
Hi,
PostgreSQL 7.1beta6 built on NetBSD-1.5/i386 fails the polygon test in
'make check'. The following change to resultmap makes all tests
(other than random :-) pass on this platform.
I don't know if this change is appropriate for all NetBSD platforms; I
have a couple of variants of hardware a
Hi,
Today I built postgresql-7.1beta6 on NetBSD-1.4.2/i386, which uses
a.out binary format. (NetBSD 1.5/i386 uses ELF.)
I found that psql needs to be linked with -ltermcap or else psql will
fail with a runtime error when used interactively:
$ psql ...
Welcome to psql, the PostgreSQL interacti
pgsql 7.1 beta.. NOT USE Delphi "Ttable"
component
Hi all.
First time I execute `make check' 10 tests failed:
float8 ... FAILED
test numerology ... FAILED
point... FAILED
lseg ... FAILED
interval ... FAILED
test geometry ... FAILED
test horology
Hello,
I have installed PosgreSQL 7 on Red Hat Linux 6.1. I am developing a
CRM system using front hand "Enhydra" and back hand as "PostgreSql". I
have encountered the problem in developing a function. The error message
I receive is fmgr_info: function 18816: cache
lookup failed. The structure of
Quoting [EMAIL PROTECTED]:
>
> We are running a PostgreSQL server on a Debian 2.2 and we have problems
> with
> the
> mothod getTimestamp() of the ResultSet class;
> we have find that if we insert a timestamp on a table, for example
> '2000-10-09 12:21:34.321+01'
> when we try to read that tuple
Alexander Klimov <[EMAIL PROTECTED]> writes:
> It is looks like failed tests are due to
> ! psql: connectDBStart() -- connect() failed: Connection refused
> ! Is the postmaster running locally
> ! and accepting connections on Unix socket '/tmp/.s.PGSQL.65432'?
What I see is a lot of
! ps
Giles Lean writes:
> Today I built postgresql-7.1beta6 on NetBSD-1.4.2/i386, which uses
> a.out binary format. (NetBSD 1.5/i386 uses ELF.)
>
> I found that psql needs to be linked with -ltermcap or else psql will
> fail with a runtime error when used interactively:
> /usr/libexec/ld.so: Undefin
Alexander Klimov writes:
> Results of second and third passes are in the attachment.
> It is looks like failed tests are due to
> ! psql: connectDBStart() -- connect() failed: Connection refused
> ! Is the postmaster running locally
> ! and accepting connections on Unix socket '/tmp/.s.PG
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> In src/test/regress/pg_regress[.sh], line 163, change
> *-*-qnx* | *beos*)
> to
> *-*-qnx* | *beos* | *solaris*)
> and rerun the tests. This will avoid using Unix domain sockets, which are
> broken on Solaris.
I was just thinking that maybe
> Company Table Structure
> create table company ( id serial PRIMARY KEY, comp_name varchar(100),
shortname varchar(20));
> Insert Function for company table
> create function insertcompany(varchar(100),varchar(20)) returns int4
as
> 'begin
> Insert into company (comp_name,shortname) values (
Sébastien BLON ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
bug with identd autentication
Long Description
Hi
The postmaster backend seems to be blocked when the identd server of the peer
accepts the connection but does not
Leandro Peracchi ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
psql core dump on login
Long Description
The default pg_hba.conf file have these two entries:
local trust
host 127.0.0.1 255.255
[EMAIL PROTECTED] writes:
> The postmaster backend seems to be blocked when the identd server of the peer
> accepts the connection but does not respond.
Yes, this is a known shortcoming --- it is (or should be) in the TODO list.
However, it hasn't been very high priority, because you shouldn't b
In current sources, try the following:
while true; do
psql -c "checkpoint" yourdb
done
(any SQL command will do, it needn't be a checkpoint)
Press control-C while it's cycling. A fair fraction of the time
I get a SEGV coredump from psql.
I've been able to replicate this on both HPUX and Linux
I said:
> In current sources, try the following:
> while true; do
> psql -c "checkpoint" yourdb
> done
> (any SQL command will do, it needn't be a checkpoint)
> Press control-C while it's cycling. A fair fraction of the time
> I get a SEGV coredump from psql.
Ah, I think I see the problem: if
[EMAIL PROTECTED] writes:
> But when change "trust" to "password" (or "crypt") psql require a password.
> Then, entering the correct password or not, psql exit with a core dump.
Stack trace from core file, please?
gdb /path/to/psql core
bt
quit
Also, where did you get yo
=?iso-8859-1?Q?BLON_S=E9bastien?= <[EMAIL PROTECTED]> writes:
> We'd like to reduce the timeout in the case of identd faillures.
> Is it possible ?
I doubt it; if the ident server dies then it's really a TCP protocol
question as to how soon the postmaster will be told that. (I do think
your remo
Hey guys,
I don't understand what you mean by "This will avoid using Unix domain
sockets, which are broken on Solaris.".
If this were the case, then the errors which are described would happen
on ALL solaris platforms wouldn't they? And other packages using Unix
domain sockets would have proble
Justin Clift <[EMAIL PROTECTED]> writes:
> If it's of any help, I get the same types of regression testing failures
> on Solaris, with the same "is the backend running?" type error
> messages.. when the installation of solaris HAS NOT had it's /etc/system
> file altered to change the amount of sha
Hi all,
I haven't been following the current thread on failed tests but I just had
some so I thought I'd mention it. If this is a repeat then I apologize.
I configured with:
./configure --enable-multibyte --enable-syslog --with-java --with-maxbackend
s=70
And the test
24 matches
Mail list logo
