BUG #1341: problem when showing resulted in the screen

From: "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1341: problem when showing resulted in the screen
Date: 2004-12-06 13:27:59
Message-ID: 20041206132759.0B2467388A8@www.postgresql.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 1341
Logged by: Pablo Borges

Email address: pablodev(at)hotmail(dot)com

PostgreSQL version: 7.4.6

Operating system: Linux Slackware

Description: problem when showing resulted in the screen

Details:

select * from teleoperador;
id | login | ip | tipo
----+----------+------------------------+------
0 | pablo | 10.0.0.106 | C
1 | builder | 10.0.0.107
10.0.0.107 | C
2 | reinaldo | 10.0.0.105 | C
(3 rows)

\d teleoperador
Table "public.teleoperador"
Column | Type | Modifiers
--------+-------------------+----------------------------------------------
----------------
id | integer | not null default
nextval('public.teleoperador_id_seq'::text)
login | character varying |
ip | character varying | not null
tipo | character(1) | not null
Indexes:
"teleoperador_pkey" primary key, btree (id)
"teleoperador_login_key" unique, btree (login)

is one bug?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-12-06 15:50:38 Re: BUG #1341: problem when showing resulted in the screen
Previous Message Frank van Vugt 2004-12-06 12:38:50 Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running