Обсуждение: PostgreSQL-9.0.1

On Thu, 2011-08-18 at 17:06 +0530, Venkat Balaji wrote:
>
> I am getting the following error when trying to install PG-9.0.1 -

<snip>

Why don't you use RPMs for that?

http://yum.pgrpms.org

(and please use 9.0.4)

Regards,
--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org  Twitter: http://twitter.com/devrimgunduz

I think you should also need 'zlib-devel', check with the rpm's list of zlib in your OS. 

---

Regards,

Raghavendra

EnterpriseDB Corporation

Blog: http://raghavt.blogspot.com/

On Thu, Aug 18, 2011 at 5:06 PM, Venkat Balaji <venkat.balaji@verse.in> wrote:

Hello Community,

I am getting the following error when trying to install PG-9.0.1 -

pg_backup_archiver.o: In function `SetOutput':

pg_backup_archiver.c:(.text+0x2b6f): undefined reference to `gzopen64'

pg_backup_files.o: In function `_StartBlob':

pg_backup_files.c:(.text+0x50d): undefined reference to `gzopen64'

pg_backup_files.o: In function `_StartData':

pg_backup_files.c:(.text+0x5e0): undefined reference to `gzopen64'

pg_backup_files.o: In function `_PrintFileData':

pg_backup_files.c:(.text+0x9f6): undefined reference to `gzopen64'

collect2: ld returned 1 exit status

make[3]: *** [pg_dump] Error 1

make[3]: Leaving directory `/home/postgres/postgresql-9.0.1/src/bin/pg_dump'

make[2]: *** [all] Error 2

make[2]: Leaving directory `/home/postgres/postgresql-9.0.1/src/bin'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/home/postgres/postgresql-9.0.1/src'

make: *** [all] Error 2

Following is the operating system version -

"[root@localhost postgresql-9.0.1]# uname -a

Linux localhost.localdomain 2.6.18-164.el5PAE #1 SMP Thu Sep 3 04:10:44 EDT 2009 i686 i686 i386 GNU/Linux"

We have successfully installed the same on other RHEL servers.

Note : zlib-1.2.3, flex-2.5.35 are installed.

Thanks

Nag

Venkat Balaji <venkat.balaji@verse.in> writes:
> I believe, there must be some options to be used with make.

No, the make command should just be "make".  Any options that are needed
would be supplied at the configure step.

> pg_backup_archiver.o: In function `SetOutput':
> pg_backup_archiver.c:(.text+0x2b6f): undefined reference to `gzopen64'

FWIW, this seems to indicate a mismatch between the zlib.h you're using
and the libz.so you're linking to.  The PG sources do not reference
gzopen64, but some versions of zlib.h conditionally #define gzopen as
gzopen64 --- in which case it'd better be used with a library that
actually provides that symbol.  Evidently the one that the linker is
finding does not.  If I had to bet based on this much information,
I'd bet on a manual zlib installation that doesn't match the system's
libz.so, and for which you forgot to do the ldconfig magic needed to get
the linker to actually pick yours instead of the /usr/lib one.

                       regards, tom lane

Hi Tom,

Thank you very much for your reply !

Before I read this post, I had successfully installed Postgres with "--without-zlib" option.

Could you please let me know what could be the impact on the database and application performance ?

I am installing PG on a brand new server (CentOS - 5.4) 32 bit. I would redo the installation with "ldconfig" option as well (i never did before).

But, we did not face this problem before on any of our servers (both on 64 bit and 32 bit). I mean we never had to manually link our libraries using "ldconfig".

Thanks

Venkat

On Fri, Aug 19, 2011 at 7:21 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Venkat Balaji <venkat.balaji@verse.in> writes:
> I believe, there must be some options to be used with make.

No, the make command should just be "make".  Any options that are needed
would be supplied at the configure step.

> pg_backup_archiver.o: In function `SetOutput':
> pg_backup_archiver.c:(.text+0x2b6f): undefined reference to `gzopen64'

FWIW, this seems to indicate a mismatch between the zlib.h you're using
and the libz.so you're linking to.  The PG sources do not reference
gzopen64, but some versions of zlib.h conditionally #define gzopen as
gzopen64 --- in which case it'd better be used with a library that
actually provides that symbol.  Evidently the one that the linker is
finding does not.  If I had to bet based on this much information,
I'd bet on a manual zlib installation that doesn't match the system's
libz.so, and for which you forgot to do the ldconfig magic needed to get
the linker to actually pick yours instead of the /usr/lib one.

                       regards, tom lane