Michael Paquier <michael(at)paquier(dot)xyz> writes:
> I would follow the practice of upstream to include both if were me
> to be consistent, but I'm also fine if you just add x509v3.h to
> be-secure-openssl.c.
Another thing that's potentially relevant here is that
be-secure-openssl.c and fe-secure-openssl.c are including
ssl-related headers in different orders. Theoretically
that shouldn't make any difference, but ...
regards, tom lane