On Wed, Sep 12, 2018 at 08:17:05PM -0400, Tom Lane wrote:
> Yeah, I was afraid of that. We could invent a typedef "pg_struct_stat"
> that maps to the right thing, but using that everywhere would be a mighty
> invasive change :-(.
There are 130 places where "struct stat " is used, so I'd rather avoid
that.
> And we can't just "#define stat __stat64" because
> that would break the calls to stat(). Or wait, maybe we could do that
> and also have a one-liner function named __stat64 that would catch the
> calls and redirect to _stat64?
I don't think I grab your point here. "#define stat __stat64" cannot
exist from the start so how would you do that?
--
Michael