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

Re: DEALLOCATE ALL

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Neil Conway" <neilc(at)samurai(dot)com>, "Marko Kreen" <markokr(at)gmail(dot)com>, PGSQL-Patches <pgsql-patches(at)postgresql(dot)org>, "Andrzej Rusin" <Andrzej(dot)Rusin(at)interia(dot)pl>
Subject: Re: DEALLOCATE ALL
Date: 2007-03-30 12:55:46
Message-ID: e51f66da0703300555m238cac13h122131e3370c6f35@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-patches
On 3/30/07, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Neil Conway escribió:
>
> > As to the implementation, calling hash_remove() in a loop seems a pretty
> > unfortunate way to clear a hash table -- adding a hash_reset() function
> > to the dynahash API would be cleaner and faster.
>
> I wonder why hash_drop cannot be used?

hash_destroy()?  Each element need separate destruction.

-- 
marko

In response to

Responses

pgsql-patches by date

Next:From: Peter EisentrautDate: 2007-03-30 12:58:00
Subject: Re: Current enums patch
Previous:From: Alvaro HerreraDate: 2007-03-30 12:43:50
Subject: Re: DEALLOCATE ALL

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