| From: | "Gaetano Mendola" <mendola(at)bigfoot(dot)com> |
|---|---|
| To: | <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
| Subject: | Re: [PATCHES] mcxt.c |
| Date: | 2003-09-09 14:53:06 |
| Message-ID: | 029301c376e2$1b3f3700$4c720b3e@mm.eutelsat.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Andrew Dunstan" <andrew(at)dunslane(dot)net> wrote:
> The particular assertion that was proposed doesn't strike me as terribly
> useful - It should be checked at the point of call rather than inside
> pstrdup, I should have thought.
Are you going to trust the client of that function ?
Here the question is not if insert a check/assert there but write a general
rule if insert and where check/assert
Regards
Gaetano Mendola
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manfred Koizar | 2003-09-09 14:56:20 | Re: plpgsql doesn't coerce boolean expressions to boolean |
| Previous Message | Tom Lane | 2003-09-09 14:44:30 | Re: Maximum table size |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera Munoz | 2003-09-09 15:14:57 | Re: [PATCHES] mcxt.c |
| Previous Message | Andrew Dunstan | 2003-09-09 13:40:27 | Re: [PATCHES] mcxt.c |