Re: [PATCHES] [HACKERS] LDAP auth
Was there ever a decision in the libcurl thread? No, not yet. Personally I'm unconvinced that we should depend on libcurl: if it's going to use openldap to do LDAP work, then the only good reason to use libcurl rather than openldap directly is if there's some clear use-case for libcurl's other features. Which no one had presented AFAIR. I'm still willing to be convinced though. I'm almost done with implementing a patch that recognizes LDAP URLs in pg_services.conf and queries an LDAP server for a connection option string. Currently I'm coding against libldap, and I intend to submit the patch that way. If there are loud calls for another library, I think I could adapt the code without much hassle. The only other protocol I can think of that might make sense is HTTP, but I personally have never heard of a web server employed that way. Yours, Laurenz Albe ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PATCHES] [HACKERS] LDAP auth
Was there ever a decision in the libcurl thread? No, not yet. Personally I'm unconvinced that we should depend on libcurl: if it's going to use openldap to do LDAP work, then the only good reason to use libcurl rather than openldap directly is if there's some clear use-case for libcurl's other features. Which no one had presented AFAIR. I'm still willing to be convinced though. I'm almost done with implementing a patch that recognizes LDAP URLs in pg_services.conf and queries an LDAP server for a connection option string. Currently I'm coding against libldap, and I intend to submit the patch that way. If there are loud calls for another library, I think I could adapt the code without much hassle. The only other protocol I can think of that might make sense is HTTP, but I personally have never heard of a web server employed that way. If you haven't already, look at the ldap auth patch in the queue for some win32 specific issues - we do not want to rely on OpenLDAP on windows, since there is a builtin version that's almost the same (close enough). (BTW, web servers are employed for *anything* these days...) //Magnus ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [PATCHES] LDAP auth
Andrew Dunstan wrote: I suggested libcurl in another context, and not so much as a means of getting at LDAP data as a means of getting config data from non-LDAP as well as LDAP sources. If all we want is LDAP then using libcurl would indeed be introducing an unnecessary dependency. In this context, though, its use seems a bit odd. Right, that's what I remember, the curl can _also_ be used to distribute authentication data, but of course LDAP is more standard. Um. LDAP is a protocol, curl is a libary. I assume you mean OpenLDAP, though. And yes, OpenLDAP is way more common than libcurl for getting LDAP data. And since libcurl depends on openldap, there's really no point in donig it unless you're going to use the *other* features of libcurl as well. //Magnus ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [PATCHES] LDAP auth
Patch applied. Thanks. --- Magnus Hagander wrote: This patch adds native LDAP auth, for those platforms that don't have PAM (such as Win32, but also unixen without PAM). On Unix, uses OpenLDAP. On win32, uses the builin WinLDAP library. //Magnus Content-Description: ldap_auth.patch [ Attachment, skipping... ] Content-Description: ldap_doc.patch [ Attachment, skipping... ] ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings -- Bruce Momjian http://candle.pha.pa.us SRA OSS, Inc. http://www.sraoss.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [PATCHES] TODO item: remove postmaster -o option
Markus Bertheau wrote: The docs say The use of this option is obsolete; all command-line options for server processes can be specified directly on the postmaster command line First, note the use of obsolete -- there are better ways to achieve what you want -- as opposed to deprecated -- the use is recommended against (for some reason to be specified). If we make a plan to remove the -o option sometime, we should use the latter and announce our intentions. That needs to be discussed, though. The above documentation is only in the development branch, so deriving a justification for removing that option from that is premature anyway. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [PATCHES] [HACKERS] Backslashes in string literals
Great patch. Applied. Thanks. --- Kevin Grittner wrote: The attached patch combines work from two patches recently posted by Bruce Momjian, along with a necessary change to guc.c which is missing from those patches. Please ignore all prior patches with this subject line and consider this a rollup. -Kevin [ Attachment, skipping... ] ---(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 -- Bruce Momjian http://candle.pha.pa.us SRA OSS, Inc. http://www.sraoss.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [PATCHES] [HACKERS] Zeroing damaged pages
Bruce Momjian pgman@candle.pha.pa.us writes: + /* Even if zero_damaged_pages is true, we don't want autovacuum zeroing. */ + zero_damaged_pages = false; This is completely incorrect; you need to set the variable via GUC, else it will still be overridden from postgresql.conf if a SIGHUP arrives. I believe this would work: SetConfigOption(zero_damaged_pages, false, PGC_SUSET, PGC_S_SESSION); regards, tom lane ---(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] [HACKERS] Zeroing damaged pages
Tom Lane wrote: Bruce Momjian pgman@candle.pha.pa.us writes: + /* Even if zero_damaged_pages is true, we don't want autovacuum zeroing. */ + zero_damaged_pages = false; This is completely incorrect; you need to set the variable via GUC, else it will still be overridden from postgresql.conf if a SIGHUP arrives. I believe this would work: SetConfigOption(zero_damaged_pages, false, PGC_SUSET, PGC_S_SESSION); Done. -- Bruce Momjian http://candle.pha.pa.us SRA OSS, Inc. http://www.sraoss.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
