On Sat, Mar 5, 2011 at 2:47 AM, Arnold, Sandra <[email protected]> wrote:
> All of a sudden the psql for 9.0 is giving me the error below. The dump > is just a partial dump. Is this a known issue? It was working for about 4 > days after I installed the software until around lunch time today. I did > the install using the current one-click installer provided by EnterpriseDB. > > > *** glibc detected *** /app/PostgreSQL/9.0/bin/psql: free(): invalid next > size (fast): 0x0000000015b46b20 *** > ======= Backtrace: ========= > /lib64/libc.so.6[0x358167230f] > /lib64/libc.so.6(cfree+0x4b)[0x358167276b] > /app/PostgreSQL/9.0/bin/psql[0x4139b4] > /app/PostgreSQL/9.0/bin/psql[0x414e44] > /app/PostgreSQL/9.0/bin/psql[0x415a68] > /app/PostgreSQL/9.0/bin/psql[0x408d82] > /app/PostgreSQL/9.0/bin/psql[0x40d9d6] > /app/PostgreSQL/9.0/bin/psql[0x40fa7e] > /lib64/libc.so.6(__libc_start_main+0xf4)[0x358161d994] > /app/PostgreSQL/9.0/bin/psql[0x403a69] > ======= Memory map: ======== > 00400000-00456000 r-xp 00000000 fd:01 691534 > /app/PostgreSQL/9.0/bin/psql > 00655000-00656000 rw-p 00055000 fd:01 691534 > /app/PostgreSQL/9.0/bin/psql > 00656000-00657000 rw-p 00656000 00:00 0 > 15b2e000-15b4f000 rw-p 15b2e000 00:00 0 > [heap] > 3485e00000-3485e03000 r-xp 00000000 fd:01 693115 > /app/PostgreSQL/9.0/lib/libtermcap.so.2 > 3485e03000-3486002000 ---p 00003000 fd:01 693115 > /app/PostgreSQL/9.0/lib/libtermcap.so.2 > 3486002000-3486003000 rw-p 00002000 fd:01 693115 > /app/PostgreSQL/9.0/lib/libtermcap.so.2 > 354e400000-354e402000 r-xp 00000000 fd:00 229449 > /lib64/libcom_err.so.2.1 > 354e402000-354e601000 ---p 00002000 fd:00 229449 > /lib64/libcom_err.so.2.1 > 354e601000-354e602000 rw-p 00001000 fd:00 229449 > /lib64/libcom_err.so.2.1 > 3581200000-358121c000 r-xp 00000000 fd:00 229379 > /lib64/ld-2.5.so > 358141b000-358141c000 r--p 0001b000 fd:00 229379 > /lib64/ld-2.5.so > 358141c000-358141d000 rw-p 0001c000 fd:00 229379 > /lib64/ld-2.5.so > 3581600000-358174e000 r-xp 00000000 fd:00 229386 > /lib64/libc-2.5.so > > > Please follow below steps to resolve this issue: *Step 1:* Install Libedit module from Yum Repository. [root@239435-db9 ~]# yum install libedit.x86_64 [root@239435-db9 ~]# rpm -q libedit.x86_64 libedit-2.11-2.20080712cvs.el5 *Step 2:* Identify the location of installed libedit binary location. [root@239435-db9 ~]# rpm -q libedit.x86_64 --filesbypkg libedit /usr/lib64/libedit.so.0 libedit /usr/lib64/libedit.so.0.0.27 libedit /usr/share/doc/libedit-2.11 libedit /usr/share/doc/libedit-2.11/COPYING libedit /usr/share/doc/libedit-2.11/ChangeLog libedit /usr/share/doc/libedit-2.11/THANKS [root@239435-db9 ~]# pwd /root *Step 3*: Take the backup of bundled libedit binary [root@239435-db9 ~]# cd /opt/PostgreSQL/9.0/lib/ [root@239435-db9 lib]# ls -l libedit* -rwxr-xr-- 1 root daemon 192738 Dec 14 04:46 libedit.so [root@239435-db9 lib]# mv libedit.so libedit.so.bk *Step 4:* Soft link the newly installed libedit binary to PostgreSQL installed location [root@239435-db9 lib]# ln -s /usr/lib64/libedit.so.0 /opt/PostgreSQL/9.0/lib/libedit.so *Step 5:* Connect to the Database using PSQL binary. --Raghu Ram > Thanks, > > *Sandra Arnold* > *Senior Database Administrator* > *Contractor to DOE/OSTI* > *NCI, Inc.* > *Oak Ridge, TN* > *(865) 576-0054 (work)* > *(865) 567-7553 (cell)* > *[email protected]* > >
