Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: move hash_any from hash to utils
- From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
- Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: move hash_any from hash to utils
- Date: Fri, 30 May 2008 19:23:03 -0400
- Message-id: <20080530232303(dot)GB12750(at)alvh(dot)no-ip(dot)org>
Zdenek Kotala wrote: > I'm trying to cleanup header dependences and it seems hash_any and > hash_uint32 function is candidate to move into separate c file in > backend/utils/misc directory. It significantly reduce amount of > unnecessary includes from files like network.c ( > http://doxygen.postgresql.org/network_8c.html) > > Any comments? I considered that too, so +1. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
- References:
- move hash_any from hash to utils
- From: Zdenek Kotala
- move hash_any from hash to utils
- Prev by Date: Re: Core team statement on replication in PostgreSQL
- Next by Date: Re: Core team statement on replication in PostgreSQL
- Previous by thread: move hash_any from hash to utils
- Next by thread: Shouldn't Natural JOINs Follow FK Constraints?
- Indexes: