| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | postgres user <postgresuser1989(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Re: Using different GCC, CFLAGS, CCFLAGS and CPPFLAGS to compile Postgres and PostGIS? |
| Date: | 2017-02-02 05:20:39 |
| Message-ID: | 1556.1486012839@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
postgres user <postgresuser1989(at)gmail(dot)com> writes:
> Also can you explain if I built Postgres from source on one platform lets
> say RHEL_6 and deployed its artifacts like its binaries, libs and share on
> a CentOS
In general I would not expect that to work. RHEL to CentOS is a special
case because they're really the same platform --- if it didn't work, you'd
have grounds to file a bug against the CentOS maintainers. But, say, RHEL
to Debian likely wouldn't work, and neither set of maintainers would
consider an ABI-compatibility complaint to be a valid bug.
> and tried building extensions against Postgres on CentOS are there
> any dangers of doing that?
Doesn't matter if the core system itself doesn't work, which it wouldn't
in cross-platform cases.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | alexanderfelipewo | 2017-02-02 11:27:45 | pgbouncer increase pool_size, reload does not work |
| Previous Message | postgres user | 2017-02-02 05:11:18 | Re: Using different GCC, CFLAGS, CCFLAGS and CPPFLAGS to compile Postgres and PostGIS? |