[HACKERS] Man Lebt nur einmal - probiers aus ! of clarity I think -- who've faced the
Verpassen Sie nichts am Lebem - Sie werden fuhlen was unsere Kunden bestatigen! Preise die keine Konkurrenz kennen - keine versteckte Kosten - Visa verifizierter Onlineshop - Kein peinlicher Arztbesuch erforderlicht - Kostenlose, arztliche Telefon-Beratung - Diskrete Verpackung und Zahlung - Kein langes Warten - Auslieferung innerhalb von 2-3 Tagen - Bequem und diskret online bestellen. Jetzt bestellen - und vier Pillen umsonst erhalten http://ayvbpcu.continuemany.hk/?538804528889
[HACKERS] 2PC-induced lockup
The following command sequence appears to lock up the database system: BEGIN; LOCK pg_authid; PREPARE TRANSACTION 'foo'; \q After that you can't connect anymore, even in single-user mode. The only way I could find is to clear out the pg_twophase directory, but I'm not sure whether it is safe to do that. Should this be prevented somehow, and is there a better recovery path? -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[HACKERS] GSSAPI patch
I have applied the latest version of the GSSAPI patch with only minor further fixes. I'm still working on the documentation part and will make a separate commit with that as soon as I can. I'd appreciate it if people can run tests with this on some other platforms (I've only tested on Ubuntu linux and Win32). Specifically, I'm certain that the autoconf stuff will need to be expanded a bit in order to work for them all. /Magnus ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] 2PC-induced lockup
is it good to allow locks on system tables at all? i am not so sure. have seen some disaster in the past with that. just consider somebody placing ACCESS EXCLUSIVE LOCK on a system table. it is basically denial of service. best regards, hans On Jul 10, 2007, at 3:14 PM, Peter Eisentraut wrote: The following command sequence appears to lock up the database system: BEGIN; LOCK pg_authid; PREPARE TRANSACTION 'foo'; \q After that you can't connect anymore, even in single-user mode. The only way I could find is to clear out the pg_twophase directory, but I'm not sure whether it is safe to do that. Should this be prevented somehow, and is there a better recovery path? -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings -- Cybertec Geschwinde Schönig GmbH Gröhrmühlgasse 26, 2700 Wiener Neustadt Tel: +43/1/205 10 35 / 340 www.postgresql.at, www.cybertec.at
Re: [HACKERS] 2PC-induced lockup
Peter Eisentraut [EMAIL PROTECTED] writes: The following command sequence appears to lock up the database system: BEGIN; LOCK pg_authid; PREPARE TRANSACTION 'foo'; \q After that you can't connect anymore, even in single-user mode. The only way I could find is to clear out the pg_twophase directory, but I'm not sure whether it is safe to do that. Should this be prevented somehow, and is there a better recovery path? AFAICS this is just one of many ways in which a superuser can shoot himself in the foot; I'm not eager to try to prevent it. Right offhand, clearing pg_twophase while the system is stopped should be safe enough. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] GSSAPI patch
Magnus Hagander [EMAIL PROTECTED] writes: I'd appreciate it if people can run tests with this on some other platforms (I've only tested on Ubuntu linux and Win32). Specifically, I'm certain that the autoconf stuff will need to be expanded a bit in order to work for them all. What sort of tests have you got in mind? 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: [HACKERS] GSSAPI patch
On Tue, Jul 10, 2007 at 10:43:22AM -0400, Tom Lane wrote: Magnus Hagander [EMAIL PROTECTED] writes: I'd appreciate it if people can run tests with this on some other platforms (I've only tested on Ubuntu linux and Win32). Specifically, I'm certain that the autoconf stuff will need to be expanded a bit in order to work for them all. What sort of tests have you got in mind? The one I'm most looking for is simply being able to build with GSSAPI enabled. I don't foresee any problems between implementations (there could be of course, but the standard defines the protocol), but I'm sure headers and libraries could be in different places and have different names. Actually testing the authentication itself is of course a bonus :-) I've only tested it against Active Directory, but IIRC Henry has used a Unix based Kerberos server. But more testing is always good. //Magnus ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] GSSAPI patch
Magnus Hagander wrote: On Tue, Jul 10, 2007 at 10:43:22AM -0400, Tom Lane wrote: Magnus Hagander [EMAIL PROTECTED] writes: I'd appreciate it if people can run tests with this on some other platforms (I've only tested on Ubuntu linux and Win32). Specifically, I'm certain that the autoconf stuff will need to be expanded a bit in order to work for them all. What sort of tests have you got in mind? The one I'm most looking for is simply being able to build with GSSAPI enabled. I don't foresee any problems between implementations (there could be of course, but the standard defines the protocol), but I'm sure headers and libraries could be in different places and have different names. this sounds more like a headsup to the buildfarm owners to add that flag to their configuration ? Stefan ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Updated tsearch documentation
Thanks, I applied this patch and rebuild HTML version. I was wondering how I was going to make all the changes accurately. ;-) --- Nicolas Barbier wrote: 2007/7/7, Bruce Momjian [EMAIL PROTECTED]: FYI, I have massively reorganized the text search documentation and it is getting closer to something I am happy with: http://momjian.us/expire/fulltext/HTML/textsearch.html The following is the result of me proofreading, mainly searching for small mistakes such as spelling/grammatical errors (that means no document structure comments, etc). All corrections are relative to the version of the text at above URL at the time of me reading it :-). General It seems to be a recurring problem that commas are not put between the brackets when an argument is optional. For example: to_tsvector([conf_name], document TEXT) - I guess this should be to_tsvector([conf_name,] document TEXT) Full-text vs. full text and stop-word vs. stop word are not used consistently. Also, capitalization of full text searching is not used consistently. -- Bruce Momjian [EMAIL PROTECTED] http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[HACKERS] Tipos abstractos definidos por el usuarios
Estoy interesada en saber como se hace tratamiento de Objetos en postgresql; especìficamente necesito saber como se encapsulan data y metodos en una clase y las primitivas para lograrlo así como puedo definir tipos donde se encapsulen datos con mètodos y se declaren referncias (apuntadores) a estos objetos y clases. Por favor si alguien a trabajado en esto aviseme. Saludos. Livia - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
[HACKERS] Tipos abstractos definidos por el usuarios
Estoy interesada en saber como se hace tratamiento de Objetos en postgresql; especìficamente necesito saber como se encapsulan data y metodos en una clase y las primitivas para lograrlo así como puedo definir tipos donde se encapsulen datos con mètodos y se declaren referncias (apuntadores) a estos objetos y clases. Por favor si alguien a trabajado en esto aviseme. Saludos. Livia - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
Re: [HACKERS] GSSAPI patch
Stefan Kaltenbrunner wrote: Magnus Hagander wrote: On Tue, Jul 10, 2007 at 10:43:22AM -0400, Tom Lane wrote: Magnus Hagander [EMAIL PROTECTED] writes: I'd appreciate it if people can run tests with this on some other platforms (I've only tested on Ubuntu linux and Win32). Specifically, I'm certain that the autoconf stuff will need to be expanded a bit in order to work for them all. What sort of tests have you got in mind? The one I'm most looking for is simply being able to build with GSSAPI enabled. I don't foresee any problems between implementations (there could be of course, but the standard defines the protocol), but I'm sure headers and libraries could be in different places and have different names. this sounds more like a headsup to the buildfarm owners to add that flag to their configuration ? Yes, but I'd like to see it tested on a couple of more platforms before that :-) But hey, please go ahead... //Magnus ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] GSSAPI patch
On Jul 10, 2007, at 7:49 AM, Magnus Hagander wrote: On Tue, Jul 10, 2007 at 10:43:22AM -0400, Tom Lane wrote: Magnus Hagander [EMAIL PROTECTED] writes: I'd appreciate it if people can run tests with this on some other platforms (I've only tested on Ubuntu linux and Win32). Specifically, I'm certain that the autoconf stuff will need to be expanded a bit in order to work for them all. What sort of tests have you got in mind? The one I'm most looking for is simply being able to build with GSSAPI enabled. I don't foresee any problems between implementations (there could be of course, but the standard defines the protocol), but I'm sure headers and libraries could be in different places and have different names. Actually testing the authentication itself is of course a bonus :-) I've only tested it against Active Directory, but IIRC Henry has used a Unix based Kerberos server. But more testing is always good. //Magnus Yes, I was using a Heimdal Kerberos server and Solaris 9 or MIT GSSAPI client libraries. (Client means Kerberos client so it's both client and server for Postgres.) I just DL'ed the 2007-07-10 08:16:17 snapshot and I don't see any reference to gss or GSS in configure.in. Should I wait for tomorrow's snapshot tarball? The opinions expressed in this message are mine, not those of Caltech, JPL, NASA, or the US Government. [EMAIL PROTECTED], or [EMAIL PROTECTED] ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] GSSAPI patch
Henry B. Hotz [EMAIL PROTECTED] writes: I just DL'ed the 2007-07-10 08:16:17 snapshot and I don't see any reference to gss or GSS in configure.in. Should I wait for tomorrow's snapshot tarball? Either that or pull from the CVS server, cf http://developer.postgresql.org/pgdocs/postgres/cvs.html The snapshots are only made once a day, but the anoncvs server updates every hour. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] 2PC-induced lockup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jul 10, 2007 at 10:41:31AM -0400, Tom Lane wrote: Peter Eisentraut [EMAIL PROTECTED] writes: The following command sequence appears to lock up the database system: BEGIN; LOCK pg_authid; PREPARE TRANSACTION 'foo'; \q After that you can't connect anymore, even in single-user mode. The only way I could find is to clear out the pg_twophase directory, but I'm not sure whether it is safe to do that. Should this be prevented somehow, and is there a better recovery path? AFAICS this is just one of many ways in which a superuser can shoot himself in the foot; I'm not eager to try to prevent it. Right offhand, clearing pg_twophase while the system is stopped should be safe enough. It might make sense then to clear the pg_twophase directory on DB startup. Nobody would expect the locks to persist a database restart -- or am I way off? Regards - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGlFdxBcgs9XrR2kYRAp9/AJ4s8fBkhtaxqfu0QxBhSN2lCi++zgCfRsS9 Jpjv6513ubPtfldf2fItzj0= =KAW0 -END PGP SIGNATURE- ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] 2PC-induced lockup
[EMAIL PROTECTED] writes: On Tue, Jul 10, 2007 at 10:41:31AM -0400, Tom Lane wrote: Right offhand, clearing pg_twophase while the system is stopped should be safe enough. It might make sense then to clear the pg_twophase directory on DB startup. blink I fear you have 100% misunderstood the point. The *only* reason for that feature is to survive DB crashes. regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
