Bounced bugreport

From: Leon <leon(at)udmnet(dot)ru>
To: pgsql-general(at)postgresql(dot)org
Subject: Bounced bugreport
Date: 1999-07-01 18:42:48
Message-ID: 377BB6A8.99CB4C73@udmnet.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

This bugreport has bounced off owner-bugs(at)postgreSQL(dot)org
I think this is very silly not to allow bugreports from
"not members"

Your name :Leonid Zubatov
Your email address :leon(at)udmnet(dot)ru

System Configuration
---------------------
Architecture :intel pentium

Operating System :Linux redhat 5.9 kernel 2.2.3-5

PostgreSQL version : PostgreSQL-6.5

Compiler used :gcc 2.7.2.3

Please enter a FULL description of your problem:
------------------------------------------------
I discovered this problem first trying to create a table with a primary
key from a C program using PQexec. The table is always successfully
created, but program dies with core dump immediately after that.

After a bit of investigation I found that any query which produces
NOTICE from backend crashes the program. These statements are
EXPLAIN, create table with FOREIGN KEY.

There is also something wrong with psql application: it prints all
NOTICES from backend twice.

And, by the way, psql doesn't feel the up-arrow key
on the keyboard, it prints symbols ^[[A when I press up-arrow.
There wasn't such problem with Postgres 6.4.

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------

Simply give one of described commands to the backend from a C program
via PQexec function

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------

Have no idea :)

-
Leon.

Browse pgsql-general by date

  From Date Subject
Next Message Alex Shnitman 1999-07-01 21:51:21 Help with upgrading old 6.1 installation on Irix5
Previous Message Anja Speerforck 1999-07-01 17:14:16 Re: [GENERAL] JOIN exclusion problem