Thread: Data Recovery
Is there any way to recover data after a mistaken delete query, using the binary data files? For example, can I make a database return to the state it was one day ago? Thanks in advance, Vangelis Natsios
Hi, I have downloaded the latest tar ball and am attempting to install this on SuSE 9.1. When I run configure I get several error messages and don't know how to resolve them. The configure command and output are below. Any help is appreciated. ./configure --prefix=/usr/local/pgsql_8.0b3 --disable-rpath --with-pgport=5480 --with-perl --with-python --with-tcl --with-openssl --enable-thread-safety --enable-debug --enable-cassert --enable-depend --with-libraries=/lib:/usr/local/lib/python2.3/lib-dynload checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking which template to use... linux checking whether to build with 64-bit integer date/time support... no checking whether NLS is wanted... no checking for default port number... 5480 checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking how to turn off strict aliasing in gcc... -fno-strict-aliasing configure: using CFLAGS=-O2 -fno-strict-aliasing -g checking whether the C compiler still works... yes checking how to run the C preprocessor... gcc -E checking allow thread-safe client libraries... yes checking whether to build with Tcl... yes checking whether to build Perl modules... yes checking whether to build Python modules... yes checking whether to build with Kerberos 4 support... no checking whether to build with Kerberos 5 support... no checking whether to build with PAM support... no checking whether to build with Rendezvous support... no checking whether to build with OpenSSL support... yes configure: using CPPFLAGS=-D_GNU_SOURCE configure: using LDFLAGS= -L/lib -L/usr/local/lib/python2.3/lib-dynload checking for gawk... gawk checking for flex... /usr/bin/flex checking whether ln -s works... yes checking for ld used by GCC... /usr/i486-suse-linux/bin/ld checking if the linker (/usr/i486-suse-linux/bin/ld) is GNU ld... yes checking for ranlib... ranlib checking for lorder... no checking for tar... /bin/tar checking for strip... strip checking whether it is possible to strip libraries... yes checking for bison... bison -y configure: WARNING: *** If you are going to modify the grammar files or build from CVS, the installed *** version of Bison is too old. Bison version 1.875 or later is required. checking for perl... /usr/bin/perl checking for Perl archlibexp... /usr/lib/perl5/5.8.0/i586-linux-thread-multi checking for Perl privlibexp... /usr/lib/perl5/5.8.0 checking for Perl useshrplib... true checking for flags to link embedded Perl... /usr/lib/perl5/5.8.0/i586-linux-thread-multi/auto/DynaLoader/DynaLoader.a -L/usr/lib/perl5/5.8.0/i586-linux-thread-multi/CORE -lperl -lnsl -ldl -lm -lpthread -lc -lcrypt -lutil checking for python... /usr/local/bin/python checking for Python distutils module... yes checking Python installation directories... /usr/local/lib/python2.3 checking how to link an embedded Python application... -L/usr/local/lib/python2.3/config -lpthread -ldl -lutil -lm -lpython2.3 checking for main in -lbsd... no checking for setproctitle in -lutil... no checking for main in -lm... yes checking for main in -ldl... yes checking for main in -lnsl... yes checking for main in -lsocket... no checking for main in -lipc... no checking for main in -lIPC... no checking for main in -llc... no checking for main in -ldld... no checking for main in -lld... no checking for main in -lcompat... no checking for main in -lBSD... no checking for main in -lgen... no checking for main in -lPW... no checking for main in -lresolv... yes checking for library containing getopt_long... none required checking for main in -lunix... no checking for library containing crypt... -lcrypt checking for library containing fdatasync... none required checking for shmget in -lcygipc... no checking for readline... no configure: error: readline library not found If you have readline already installed, see config.log for details on the failure. It is possible the compiler isn't looking in the proper directory. Use --without-readline to disable readline support.
>Don´t forget to remove your old bison BEFORE "gmake install": >type 'rpm -q -a|grep bison' >you´ll get the installed bison package, >type 'rpm -e <what you just got>' >to remove it > >You need the readline-devel-package, because you need the headers for readline. > >If you ever get such an error like the one with readline while running >configure, you can be quite sure, that you need a corresponding devel-package. > > > Thanks for the response. I installed the readline-devel package but have not found a bison rpm for suse at the proper revision so I ignored the warning. The rest of the install process went very easy. Hopefully not having the latest version of bison won't create problems later on. Mike