Skip site navigation (1)
Skip section navigation (2)
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)
Peripheral Links
Header And Logo
|
Site Navigation
move hash_any from hash to utils
- From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
- To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
- Subject: move hash_any from hash to utils
- Date: Fri, 30 May 2008 21:02:51 +0200
- Message-id: <48404F5B(dot)9090201(at)sun(dot)com>
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? Zdenek
- Follow-Ups:
- Re: move hash_any from hash to utils
- From: Alvaro Herrera
- Re: move hash_any from hash to utils
- Prev by Date: Pgsql-hackers
- Next by Date: Re: Core team statement on replication in PostgreSQL
- Previous by thread: Pgsql-hackers
- Next by thread: Re: move hash_any from hash to utils
- Indexes: