From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | Constantin Teodorescu <teo(at)flex(dot)ro> |
Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, PostgreSQL Hacker <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] memory destruction in 6.4 |
Date: | 1998-12-08 09:45:14 |
Message-ID: | 199812080945.SAA06847@srapc451.sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>Tatsuo Ishii wrote:
>>
>> While investigating a user's complaint, I have found some memory
>> destructions in 6.4 source using purify.
>>
>> (1) parser/gram.y:fmtId()
>>
>> It writes n+3 bytes into n+1 byte-long memory area if mixed case or
>> non-ascii identifiers given.
>
>Could that be also the cause for the two bugs that I have been reported
>some time ago occuring when object names contain spaces ?
>
>PostgreSQL 6.4 on RedHat Linux i386, 2.0.36 Kernel
>
>THE FIRST ONE
>=============
>test=>create table students (id int4, name text);
>CREATE
>test=> create view "my view" as select * from students;
>CREATE
>test=> select * from "my view";
>ERROR: nodeRead: Bad type 0
>
>
>THE SECOND ONE
>==============
>test=> create sequence student_id;
>CREATE
>test=> create table "my students" (id int4 default
>nextval('student_id'), name text);
>ERROR: my: Table does not exist.
Sorry, but my patches seem not to fix your problems.
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Broytmann | 1998-12-08 12:59:33 | Re: [HACKERS] Date/time on glibc2 linux |
Previous Message | Constantin Teodorescu | 1998-12-08 09:32:52 | Re: [HACKERS] memory destruction in 6.4 |