| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | tjo(at)acm(dot)org |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: recompliing c-language functions with new releases of postgres |
| Date: | 2006-05-24 23:04:04 |
| Message-ID: | 3013.1148511844@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"TJ O'Donnell" <tjo(at)acm(dot)org> 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 major pg changes, such as
> 7.3 to 7.4, or 8.0 to 8.1?
Uh, no, not really; see complaint from Thomas Hallgren in -hackers
just yesterday. We don't normally change internal APIs in patch
releases; in fact we don't change anything we don't have to. But
we will change 'em if needed to fix a bug.
You might want to eyeball the proposed "magic block" for loadable
modules:
http://archives.postgresql.org/pgsql-patches/2006-05/msg00124.php
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nishad Prakash | 2006-05-24 23:14:46 | New DBs from existing schemas |
| Previous Message | TJ O'Donnell | 2006-05-24 22:43:10 | recompliing c-language functions with new releases of postgres |