Re: [PATCHES] related problem of path by msvc
> Ah...I am sorry in spam mail.:-( > It is this surely.. > > Sorry..all This patch looks like it has some weird combination of unix and windows line endings. Was that intentional? //Magnus ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [PATCHES] related problem of path by msvc
Hi Magnus. From: "Magnus Hagander" This patch looks like it has some weird combination of unix and windows line endings. Was that intentional? Ea? No, did I miss something? Regards, Hiroshi Saito ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [PATCHES] related problem of path by msvc
> > This patch looks like it has some weird combination of unix and > > windows line endings. Was that intentional? > > Ea? No, did I miss something? When I open the patch, the first part of it has windows line endings and the second part has unix line endings. //Magnus ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [PATCHES] [HACKERS] Simplifying "standby mode"
On Wed, 2006-09-06 at 12:01 -0400, Bruce Momjian wrote: > Simon Riggs wrote: > > > > Likely to be completed by end of next week now, submitted in chunks: > > > > 1. Notes on restartable recovery Included here > > 2. Notes on standby functionality > > 3. discussion on rolling your own record-level polling using > > pg_xlogfile_name_offset() > > > 4. pg_standby.c sample code > > I need #4 long before the end of _this_ week, or it is going to be > rejected for 8.2. The documentation can be added even during beta, > though the earlier the better so it can be tested. I guess I was thinking to put #4 in the docs rather than contrib... but I won't be able to make this deadline either way now. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com Index: doc/src/sgml/backup.sgml === RCS file: /projects/cvsroot/pgsql/doc/src/sgml/backup.sgml,v retrieving revision 2.83 diff -c -r2.83 backup.sgml *** doc/src/sgml/backup.sgml 17 Aug 2006 23:04:02 - 2.83 --- doc/src/sgml/backup.sgml 8 Sep 2006 17:47:46 - *** *** 855,861 Start the server. The server will go into recovery mode and ! proceed to read through the archived WAL files it needs. Upon completion of the recovery process, the server will rename recovery.conf to recovery.done (to prevent accidentally re-entering recovery mode in case of a crash later) and then --- 855,863 Start the server. The server will go into recovery mode and ! proceed to read through the archived WAL files it needs. Should the ! recovery be terminated because of an external error, the server can ! simply be restarted and it will continue recovery. Upon completion of the recovery process, the server will rename recovery.conf to recovery.done (to prevent accidentally re-entering recovery mode in case of a crash later) and then *** *** 935,941 recover to such a time, you must go back to your previous base backup and roll forward from there.) ! Recovery Settings --- 937,957 recover to such a time, you must go back to your previous base backup and roll forward from there.) ! ! ! ! If recovery finds a corruption in the WAL data then recovery will ! complete at that point and the server will not start. The recovery ! process could be re-run from the beginning, specifying a ! recovery target so that recovery can complete normally. ! If recovery fails for an external reason, such as a system crash or ! the WAL archive has become inaccessible, then the recovery can be ! simply restarted and it will restart almost from where it failed. ! Restartable recovery works by writing a restartpoint record to the control ! file at the first safely usable checkpoint record found after ! checkpoint_timeout seconds. ! ! Recovery Settings ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [PATCHES] [HACKERS] Fix linking of OpenLDAP libraries
"Albe Laurenz" <[EMAIL PROTECTED]> writes: > I did not only add them to the Makefile for interfaces/libpq, > but also everywhere something is linked against libpq in case > somebody links static. I intensely dislike that part of the patch, but will work on applying the rest. If we do need to start mentioning all of libpq's dependencies everywhere it's linked, I think it's time for a generic solution to that, instead of hacking each such place over again every time a new dependency pops up. But at the moment I'm unconvinced that we need to do it. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PATCHES] [HACKERS] Fix linking of OpenLDAP libraries
On Fri, Sep 08, 2006 at 03:20:00PM -0400, Tom Lane wrote: > "Albe Laurenz" <[EMAIL PROTECTED]> writes: > > I did not only add them to the Makefile for interfaces/libpq, > > but also everywhere something is linked against libpq in case > > somebody links static. > If we do need to start mentioning all of libpq's dependencies everywhere > it's linked, I think it's time for a generic solution to that, instead > of hacking each such place over again every time a new dependency pops up. The business of having to include every single dependancy when linking static is quite irritating. It has almost reached the point where people are just giving up static linking because it's too much of a pain. However, if we do want to support it, the way you do it is by extending pg_config to do something like: pg_config --dynamic-lick => returns -lpq pg_config --static-link=> returns -lpq That way only people who actually want static linking need be bothered. Have a ncie day, -- Martijn van Oosterhout http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to > litigate. signature.asc Description: Digital signature
Re: [PATCHES] [HACKERS] Fix linking of OpenLDAP libraries
"Albe Laurenz" <[EMAIL PROTECTED]> writes: > Here is a new patch that replaces the previous one; it adds two > macros LDAP_LIBS_FE and LDAP_LIBS_BE for frontend and backend, > respectively. > I did not only add them to the Makefile for interfaces/libpq, > but also everywhere something is linked against libpq in case > somebody links static. Applied, but without that last part. It builds OK for me on Darwin, which is moderately picky about that sort of thing, but someone should try AIX. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
