Skip site navigation (1) Skip section navigation (2)

Re: tsearch2 memory alloc checks

From: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: tsearch2 memory alloc checks
Date: 2003-09-28 09:28:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
On Sat, 27 Sep 2003, Bruce Momjian wrote:
> This has been saved for the 7.5 release:
> 	http:/

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.

In response to


pgsql-patches by date

Next:From: Peter EisentrautDate: 2003-09-28 09:41:33
Subject: Re: correct NUL vs. NULL usage
Previous:From: Hiroshi InoueDate: 2003-09-28 09:18:11
Subject: Re: pgsql-server/src/backend catalog/index.c comma ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group