Re: move hash_any to utils/hash/hashfn.c
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-03-11T16:27:47Z
Lists: pgsql-hackers
On 2019-Jan-25, Alvaro Herrera wrote: > Would anybody object too hard if I move hash_any() and friends to > src/backend/utils/hash/hashfn.c and the declarations to > src/include/utils/hashutils.h? Pushed this. I ended up adding an #include of utils/hashutils.h to access/hash.h, so that any third-party code using hash_any() from the latter continues to build unbroken. I don't think this is terribly problematic -- the only issue is that those projects won't become updated to use the leaner file, but I don't think we care too much about that. If I do get pushback about this change I can definitely remove that line and watch the fireworks. Anyway, let's see what *else* breaks now ... -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Move hash_any prototype from access/hash.h to utils/hashutils.h
- af38498d4c9b 12.0 landed