From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Maksim Likharev" <mlikharev(at)aurigin(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PG crash on simple query, story continues |
Date: | 2003-07-08 18:44:53 |
Message-ID: | 25590.1057689893@sss.pgh.pa.us |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
"Maksim Likharev" <mlikharev(at)aurigin(dot)com> writes:
> ! I would say very interesting aproach,
> ! why not just
> xfrmsize = strxfrm(xfrmstr, NULL, 0);
strxfrm doesn't work that way (and if it did, it would give back a
malloc'd not a palloc'd string).
> !if error happend, xfrmlen will be (size_t)-1
No it won't; see the man page for strxfrm.
This does raise an interesting thought though: what platform are you on?
It seems to me that we've heard of buggy versions of strxfrm that write
more bytes than they're allowed to, thereby clobbering palloc's data
structures.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-07-08 18:48:11 | Re: SQL Functions and plan time |
Previous Message | Richard Welty | 2003-07-08 18:41:53 | Re: Is Postgres broken in Red Hat 9? |
From | Date | Subject | |
---|---|---|---|
Next Message | Maksim Likharev | 2003-07-08 18:57:18 | Re: PG crash on simple query, story continues |
Previous Message | Maksim Likharev | 2003-07-08 17:14:55 | Re: PG crash on simple query, story continues |