Re: Why repalloc() != realloc() ?

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

Peripheral Links

Text Size: Normal / Large
Donate
Contact

The world's most advanced open source database.

Re: Why repalloc() != realloc() ?

From:	Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To:	Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc:	Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject:	Re: Why repalloc() != realloc() ?
Date:	2004-06-02 03:53:39
Message-ID:	20040602035339.GC2019@dcc.uchile.cl (view raw or flat)
Thread:
Lists:	pgsql-hackers

On Tue, Jun 01, 2004 at 11:39:57PM -0400, Tom Lane wrote:

> > I assume this is because the NULL pointer would not know what context it
> > belongs to,
> 
> That's a sufficient reason from my point of view.

Right, you've convinced me.  Just wanted to know if I could save three
lines of code.  Probably not a compelling reason to change the behavior.

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"El realista sabe lo que quiere; el idealista quiere lo que sabe" (Anónimo)

In response to

Re: Why repalloc() != realloc() ? at 2004-06-02 03:39:57 from Tom Lane

pgsql-hackers by date

Next: From: Bruce Momjian Date: 2004-06-02 03:59:14

Subject: Re: Nested transactions and tuple header info

Previous: From: Alvaro Herrera Date: 2004-06-02 03:50:42

Subject: Re: Nested transactions and tuple header info

Next:	From: Bruce Momjian	Date: 2004-06-02 03:59:14
	Subject: Re: Nested transactions and tuple header info
Previous:	From: Alvaro Herrera	Date: 2004-06-02 03:50:42
	Subject: Re: Nested transactions and tuple header info

Search

Peripheral Links

Re: Why repalloc() != realloc() ?

In response to

pgsql-hackers by date