Re: tsearch2 memory alloc checks - Mailing list pgsql-patches

From Nigel J. Andrews
Subject Re: tsearch2 memory alloc checks
Date
Msg-id Pine.LNX.4.21.0309280938570.8264-100000@ponder.fairway2k.co.uk
Whole thread Raw
In response to Re: tsearch2 memory alloc checks  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: tsearch2 memory alloc checks  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
On Sat, 27 Sep 2003, Bruce Momjian wrote:
>
> This has been saved for the 7.5 release:
>
>     http:/momjian.postgresql.org/cgi-bin/pgpatches2

Are you sure Bruce? I'd say this is bug fixing.

Although it doesn't fix the underlying cause of the fault it does cover the
specific fault generated and reported by someone. Athough that was running in
a 7.3 server I believe, this addresses the same fault in the 7.4 contrib.


>
> ---------------------------------------------------------------------------
>
> Nigel J. Andrews wrote:
> >
> > This should apply cleanly to cvs tip.
> >
> > I've not changed any malloc/calloc to palloc. It looks to me that these memory
> > areas are for the lifetime of the backend and in the interests of not breaking
> > something that's not broken I left alone.
> >
> > Note for anyone reading this and wanting it for tsearch-v2-stable (i.e. for 7.3
> > backend) this patch probably will not apply cleanly to that source. It should
> > be simple enough to see what's going on and apply the changes by hand if need
> > be.


pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pretty print for check constraints broken
Next
From: Peter Eisentraut
Date:
Subject: Re: correct NUL vs. NULL usage