"TJ O'Donnell" <[EMAIL PROTECTED]> writes:
> I understand and appreciate bug fixes, but isn't one of the purposes of
> major releases to provide some stability (say of API) within
> the major release?
Our traditional definition of API stability within a release series has
considered only the SQL l
"TJ O'Donnell" <[EMAIL PROTECTED]> writes:
Presumably, the only reason I would HAVE TO recompile
is when some header file changes. Is there any guarantee
that header files DO NOT change, for example from
7.4.5 to 7.4.8 or even 7.4.12? Can I assume that header
file changes only occur between
"TJ O'Donnell" <[EMAIL PROTECTED]> writes:
> Presumably, the only reason I would HAVE TO recompile
> is when some header file changes. Is there any guarantee
> that header files DO NOT change, for example from
> 7.4.5 to 7.4.8 or even 7.4.12? Can I assume that header
> file changes only occur bet
I have several c-language extensions to postgres that I
distribute. I generally have to recompile my code
with a new release of postgres, although sometimes it
appears that it functions properly (passes my tests at least)
without a recompile. Since my users are all on various
releases of postgre
