BUG #1340: problem when showing resulted in the screen - Mailing list pgsql-bugs

From PostgreSQL Bugs List
Subject BUG #1340: problem when showing resulted in the screen
Date
Msg-id 20041206132759.4D6FD7388DD@www.postgresql.com
Whole thread Raw
List pgsql-bugs
The following bug has been logged online:

Bug reference:      1340
Logged by:          Pablo Borges

Email address:      pablodev@hotmail.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?

pgsql-bugs by date:

Previous
From: Frank van Vugt
Date:
Subject: Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running
Next
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1341: problem when showing resulted in the screen