Re: [HACKERS] Use of zlib
Dennis Bjorklund wrote: This is the output in Fedora Core 2, and it includes readline: $ ldd /usr/bin/postgres linux-gate.so.1 => (0x0024) libpam.so.0 => /lib/libpam.so.0 (0x00cf1000) libssl.so.4 => /lib/libssl.so.4 (0x0014e000) libcrypto.so.4 => /lib/libcrypto.so.4 (0x00241000) libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x0052a000) libcom_err.so.2 => /lib/libcom_err.so.2 (0x00e56000) libz.so.1 => /usr/lib/libz.so.1 (0x00aca000) libreadline.so.4 => /usr/lib/libreadline.so.4 (0x00111000) libtermcap.so.2 => /lib/libtermcap.so.2 (0x00f25000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x00406000) libresolv.so.2 => /lib/libresolv.so.2 (0x00f8a000) libnsl.so.1 => /lib/libnsl.so.1 (0x00215000) libdl.so.2 => /lib/libdl.so.2 (0x00908000) libm.so.6 => /lib/tls/libm.so.6 (0x008a5000) libc.so.6 => /lib/tls/libc.so.6 (0x00592000) libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00a57000) libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00ccd000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x004ca000) Now, to see the things postgres really needs, as opposed to things other libraries need or that we just throw in for good measure in case somebody needs them, run this: LDFLAGS=-Wl,--as-necessary ./configure without any third-party options (like pam, openssl, kerberos ...), Alternatively, you can set the flag in src/Makefile.global This should work on FC2, which I believe has binutils 2.15. Almost every line above will disappear. cheers andrew ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Use of zlib
of course, I meant --as-needed rather than --as-necessary Andrew Dunstan wrote: Dennis Bjorklund wrote: This is the output in Fedora Core 2, and it includes readline: $ ldd /usr/bin/postgres linux-gate.so.1 => (0x0024) libpam.so.0 => /lib/libpam.so.0 (0x00cf1000) libssl.so.4 => /lib/libssl.so.4 (0x0014e000) libcrypto.so.4 => /lib/libcrypto.so.4 (0x00241000) libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x0052a000) libcom_err.so.2 => /lib/libcom_err.so.2 (0x00e56000) libz.so.1 => /usr/lib/libz.so.1 (0x00aca000) libreadline.so.4 => /usr/lib/libreadline.so.4 (0x00111000) libtermcap.so.2 => /lib/libtermcap.so.2 (0x00f25000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x00406000) libresolv.so.2 => /lib/libresolv.so.2 (0x00f8a000) libnsl.so.1 => /lib/libnsl.so.1 (0x00215000) libdl.so.2 => /lib/libdl.so.2 (0x00908000) libm.so.6 => /lib/tls/libm.so.6 (0x008a5000) libc.so.6 => /lib/tls/libc.so.6 (0x00592000) libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00a57000) libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00ccd000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x004ca000) Now, to see the things postgres really needs, as opposed to things other libraries need or that we just throw in for good measure in case somebody needs them, run this: LDFLAGS=-Wl,--as-necessary ./configure without any third-party options (like pam, openssl, kerberos ...), Alternatively, you can set the flag in src/Makefile.global This should work on FC2, which I believe has binutils 2.15. Almost every line above will disappear. cheers andrew ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Get rid of Money
Dennis Bjorklund <[EMAIL PROTECTED]> writes: > On Sun, 26 Sep 2004, Tom Lane wrote: >>> Wouldn't pg 8.0 be a good release to get rid of the type Money? >> >> (1) there is not actually consensus to get rid of it. > The doc seems to be clear about it. There is consensus that the current implementation is not good enough. That doesn't mean that everyone has bought into removing it (as opposed to rewriting it). There was a thread about this just a week or two ago, and IIRC we had at least one developer interested in attempting a rewrite for 8.1. regards, tom lane ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] CRITICAL HELP NEEDED! DEAD DB!
For starters a little more detail would be helpful, for example: What version of PostgreSQL? What OS? What compiler? What happened that caused this? Server Crash? Matthew Cott Lang wrote: Sep 24 10:22:37 snafu postgres[18306]: [2-1] LOG: database system was interrupted while in recovery at 2004-09-24 10:21:41 MST Sep 24 10:22:37 snafu postgres[18306]: [2-2] HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery. Sep 24 10:22:37 snafu postgres[18306]: [3-1] LOG: checkpoint record is at 9A/C2022368 Sep 24 10:22:37 snafu postgres[18306]: [4-1] LOG: redo record is at 9A/C2022368; undo record is at 0/0; shutdown FALSE Sep 24 10:22:37 snafu postgres[18306]: [5-1] LOG: next transaction ID: 197841225; next OID: 715436086 Sep 24 10:22:37 snafu postgres[18306]: [6-1] LOG: database system was not properly shut down; automatic recovery in progress Sep 24 10:22:37 snafu postgres[18306]: [7-1] LOG: redo starts at 9A/C20223B0 Sep 24 10:22:37 snafu postgres[18306]: [8-1] PANIC: btree_insert_redo: failed to add item Sep 24 10:22:37 snafu postgres[18299]: [2-1] LOG: startup process (PID 18306) was terminated by signal 6 Sep 24 10:22:37 snafu postgres[18299]: [3-1] LOG: aborting startup due to startup process failure Any suggestions to recover?! I'm dead in the water! Please!!! ---(end of broadcast)--- TIP 8: explain analyze is your friend ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] [ADMIN] v7.1b4 bad performance
On Sat, 17 Feb 2001, Tom Lane wrote: [skip] TL> Platform: HPUX 10.20 on HPPA C180, fast wide SCSI discs, 7200rpm (I think). TL> Minimum select(2) delay is 10 msec on this platform. [skip] TL> I vote for commit_delay = 0, unless someone can show cases where TL> positive delay is significantly better than zero delay. BTW, for modern versions of FreeBSD kernels, there is HZ kernel option which describes maximum timeslice granularity (actually, HZ value is number of timeslice periods per second, with default of 100 = 10 ms). On modern CPUs HZ may be increased to at least 1000, and sometimes even to 5000 (unfortunately, I haven't test platform by hand). So, maybe you can test select granularity at ./configure phase and then define default commit_delay accordingly. Your thoughts? Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
