From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
---|---|
To: | Karel Zak - Zakkr <zakkr(at)zf(dot)jcu(dot)cz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] memory dilemma |
Date: | 1999-12-10 11:17:05 |
Message-ID: | 3.0.1.32.19991210031705.00ed6168@mail.pacifier.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 11:28 AM 12/28/99 +0100, Karel Zak - Zakkr wrote:
>Thank for all suggestion. I finaly use in to_char() cache via static buffer,
>and if format-picture will bigger than this buffer, to_char will work as
>without cache. This solution eliminate memory leak - this solution is used
>in current datetime routines. It is good compromise.
Seems simple and safe, yes. My objection was really due to my concern
over memory leaks. The "to_char()" function will be a great help to
those porting over Oracle applications to Postgres.
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
From | Date | Subject | |
---|---|---|---|
Next Message | Vince Vielhaber | 1999-12-10 11:38:48 | Re: [HACKERS] 6.6 release |
Previous Message | Don Baccus | 1999-12-10 11:08:52 | Re: [HACKERS] RE: What database i can use? (fwd) |