Re: [HACKERS] function to return pg_user.usesysid
On Fri, 2003-02-07 at 07:03, Dr. Ernst Molitor wrote: > Hm, by the way, what about adding a function like current_userid to the > core functionality of PostgreSQL? What exactly would this do that couldn't be done by just querying pg_user directly? SELECT usesysid FROM pg_user WHERE usename = CURRENT_USER; Cheers, Neil -- Neil Conway <[EMAIL PROTECTED]> || PGP Key ID: DB3C29FC ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] PGP signing releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 To answer some of my earlier questions, here is one specific way of doing it: Tom Lane creates a PostgreSQL key, signing only, DSA, 1024 bits, that expires in 3 years. It ends up looking something like this: pub 1024D/0BB10D1D 2003-02-07 PostgreSQL (PostgreSQL signing key) <[EMAIL PROTECTED]> Tom keeps a close watch on the commits list and waits for a new version to be released. When the tarball is made, he checks it out and when satisfied, he signs it with the key. (Other people can look it over and verify it by referring to its sha1sum). Once signed, the small text file that is created is mailed to the web group (or just posted to the list). Somebody adds it to the web page, and from there to all the mirrors. Tom keeps the key secure, preferably by not keeping it on a box connected to the net. He generates a revocation certificate and gives it to Bruce, who squirrels it away until needed. Tom signs the key with his own, and perhaps with other developers who have PGP keys. People meet Tom at the conferences, exchange keys, the Web of Trust grows, and all is good in the world again. I chose Tom because he is part of the core and has (IMO) the best ability to detect problems in the source code and verify a final tarball. It doesn't really matter who has the key, actually, as long as they are sufficiently careful/paranoid about keeping it safe and offline, and at least one person in the core group has the ability to revoke it in case of an emergency. - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200302071451 -BEGIN PGP SIGNATURE- Comment: http://www.turnstep.com/pgp.html iD8DBQE+RBJovJuQZxSWSsgRAh3XAJ47eL56YmSKXJCtdAsyYzByMi+m2QCcCNjm b1tQyp1zLxkpGjhUer6FpZQ= =Hfpu -END PGP SIGNATURE- ---(end of broadcast)--- TIP 3: 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
[HACKERS] Cannot break out of createuser
It is not possible to break out of createuser with ctrl-c, ctrl-\ or kill -TERM. The reason is that this line: # Don't want to leave the user blind if he breaks # during password entry. trap 'stty echo >/dev/null 2>&1' 1 2 3 15 should be: trap 'stty echo >/dev/null 2>&1; exit 1' 1 2 3 15 or even trap 'stty echo >/dev/null 2>&1' EXIT -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "But the LORD is in his holy temple; let all the earth keep silence before him." Habakkuk 2:20 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] cvs (7/2/2003) is broken?
Hello! Just update my CVS tree and got the following errors: make[4]: Entering directory `/home/anteater/psql/pgsql/src/backend/optimizer/util' gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../../src/include -c -o clauses.o clauses.c clauses.c:2322:1: directives may not be used inside a macro argument clauses.c:2322:1: unterminated argument list invoking macro "IsA" make[4]: *** [clauses.o] Error 1 make[4]: Leaving directory `/home/anteater/psql/pgsql/src/backend/optimizer/util' make[3]: *** [util-recursive] Error 2 make[3]: Leaving directory `/home/anteater/psql/pgsql/src/backend/optimizer' make[2]: *** [optimizer-recursive] Error 2 make[2]: Leaving directory `/home/anteater/psql/pgsql/src/backend' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/anteater/psql/pgsql/src' make: *** [all] Error 2 It's a Linux based OS (RedHat) with: [anteater@neutrino pgsql]$ gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 2731 (Red Hat Linux 7.1 2.96-98) Regards, Elias PS. Please cc me as I'm not subscribed. -- http://gnewtellium.sourceforge.net MP3 is not a crime. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] [OpenFTS-general] Alpha version of contrib/tsearch is available for testing
To the OpenFTS Team, Please Accept heartiest congratulations from my company on the the release of tsearch. We are grateful and apprecite this great s/w PostgreSQL and contrib/tsearch. On Thursday 06 February 2003 12:34 am, Oleg Bartunov wrote: > Hi there, > > Teodor has finished alpha version of contrib/tsearch with > ranking support. Also, it includes OpenFTS (0.34) parser, ispell and > snowball (stemming) support. > > Comments and documentation are welcome ! > Without documentation we'll be not able to release the module ! > We need documentation with examples for beginners and advanced users. > > We plan to work on new version of OpenFTS after releasing contrib/tsearch. > > Download it from > http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/tsearch.tar.gz > It should works with 7.3 and current CVS. > > Any comments please send to Oleg Bartunov ([EMAIL PROTECTED]) and > Teodor Sigaev ( [EMAIL PROTECTED] ). > > > I'm going to vacation until March, so don't fill my mailbox :-) > > Regards, > Oleg > _ > Oleg Bartunov, sci.researcher, hostmaster of AstroNet, > Sternberg Astronomical Institute, Moscow University (Russia) > Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ > phone: +007(095)939-16-83, +007(095)939-23-83 > > > > > --- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > ___ > OpenFTS-general mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/openfts-general -- Regds Mallah Rajesh Kumar Mallah, Project Manager (Development) Infocom Network Limited, New Delhi phone: +91(11)6152172 (221) (L) ,9811255597 (M) Visit http://www.trade-india.com , India's Leading B2B eMarketplace. ---(end of broadcast)--- TIP 3: 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
[HACKERS] function to return pg_user.usesysid
Dear PostgreSQL developers, as far as I know, there is no function available to directly access the user id (pg_(shadow|user).usesysid) of the current database user, while the user's name is easily available (function current_user). For a couple of databases I'm using or designing, it is necessary to keep track of who has changed what and when - a job perfectly easy with the timetravel add-on (contrib/spi). Using usesysid instead of a user name to keep track of who has entered/changed/deleted data in a certain record offers saving a few bytes per record, so I wrote a _very small_ add-on to directly access the usesysid information, using the function GetUserId(). This is hardly worth mentioning since it consists of just a few lines of code, but maybe some other users might find it useful. If so, please feel free to make it available publicly. The few lines are available at http://mibi03.meb.uni-bonn.de/~ernst/pgsql_userid.tar.gz Hm, by the way, what about adding a function like current_userid to the core functionality of PostgreSQL? Best regards, Ernst ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Alpha version of contrib/tsearch is available for testing
New version are avaliable: isblank is replaced by isspace Thanks to Natasa Bulatovic <[EMAIL PROTECTED]> Oleg Bartunov wrote: Hi there, Teodor has finished alpha version of contrib/tsearch with ranking support. Also, it includes OpenFTS (0.34) parser, ispell and snowball (stemming) support. Comments and documentation are welcome ! Without documentation we'll be not able to release the module ! We need documentation with examples for beginners and advanced users. We plan to work on new version of OpenFTS after releasing contrib/tsearch. Download it from http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/tsearch.tar.gz It should works with 7.3 and current CVS. Any comments please send to Oleg Bartunov ([EMAIL PROTECTED]) and Teodor Sigaev ( [EMAIL PROTECTED] ). I'm going to vacation until March, so don't fill my mailbox :-) Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster -- Teodor Sigaev [EMAIL PROTECTED] ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Planning a change of representation in the planner
Hannu Krosing <[EMAIL PROTECTED]> writes: > Maybe the quicker way to avoid duplicate-element bugs (and get faster > merges) is to keep the lists ordered, so instead of just appending the > next int, you scan to the proper place and put it there (if it is not > there already). I had thought of doing that before it occurred to me to switch to a bitmap representation, but I was always afraid to --- I think it would be more buggy not less so. The compiler won't give any help in catching places where plain-list operations are applied to what should be an ordered list. If I change the struct type completely, then the compiler will help me. Also, the bitmap representation makes for a nice reduction in palloc() traffic (typically one palloc per set, not one per set element). That part of the performance gain won't be there if we just change to ordered lists. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] Incremental backup
How's this issue going on the 7.4 development tree? I saw it on the TODO list, but didn't find much on the archives of this mailing list. -- Porqué usar una base de datos relacional cualquiera, si podés usar PostgreSQL? - Martín Marqués |[EMAIL PROTECTED] Programador, Administrador, DBA | Centro de Telematica Universidad Nacional del Litoral - ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] Please apply patch
Please apply patches for contrib/ltree. ltree_73.patch.gz - for 7.3 : Fix ~ operation bug: eg '1.1.1' ~ '*.1' ltree_74.patch.gz - for current CVS Fix ~ operation bug: eg '1.1.1' ~ '*.1' Add ? operation Optimize index storage Last change needs drop/create all ltree indexes, so only for 7.4 Thank you. -- Teodor Sigaev [EMAIL PROTECTED] ltree_73.patch.gz Description: application/gzip ltree_74.patch.gz Description: application/gzip ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Planning a change of representation in the planner
Tom Lane kirjutas R, 07.02.2003 kell 06:35: > I've been thinking of doing this for a while just on efficiency grounds, > but kept putting it off because I don't expect much of any performance > gain on simple queries. (You need a dozen or so tables in a query > before the inefficiencies of the list representation really start to > hurt.) But tonight I'm thinking I'll do it anyway, because it'll also > be impervious to duplicate-element bugs. > > Comments? Maybe the quicker way to avoid duplicate-element bugs (and get faster merges) is to keep the lists ordered, so instead of just appending the next int, you scan to the proper place and put it there (if it is not there already). Ordered lists are also much faster ( just O(N) ) to compare/union/intersect. -- Hannu Krosing <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Status report: regex replacement
Tatsuo Ishii kirjutas R, 07.02.2003 kell 04:03: > > UTF-8 seems to be the most popular, but even XML standard requires all > > compliant implementations to deal with at least both UTF-8 and UTF-16. > > I don't think PostgreSQL is going to natively support UTF-16. By natively, do you mean "as backend storage" format or "as supported client encoding" ? -- Hannu Krosing <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] A couple of small fixes for 7.3.2 buglets
The patch below fixes a pair of little typos in a language localization file, and adds a few more shared libraries to the list of such that libpq might depend on. (I need them to get things to work properly with Kerberos 5 under NetBSD, where the lack of them breaks libpgtcl.so run-time dynamic linking, so e.g. pgaccess won't work.) Incidentally, to actually get Kerberos 5 support under NetBSD, I have to do the following: % INCLUDES="-I/usr/include/krb5"; export INCLUDES % LIBS="-lkrb5 -lkrb -lcrypto -lasn1 -lcom_err -lroken"; export LIBS % ./configure --with-krb5=/usr [...] If there is a way to get this information into the configure script, that would be a Good Thing. :-) -tih *** src/bin/pg_dump/po/pt_BR.po~Tue Dec 10 21:00:27 2002 --- src/bin/pg_dump/po/pt_BR.po Fri Feb 7 07:36:13 2003 *** *** 189,196 msgstr " -Z 0-9 nível de compressão para formatos comprimidos\n" #: pg_dump.c:675 pg_dumpall.c:238 pg_restore.c:396 ! msgid " --help show this help, then exit\vn" ! msgstr " --help mostra essa ajuda, e termina\vn" #: pg_dump.c:676 pg_dumpall.c:239 pg_restore.c:397 msgid " --versionoutput version information, then exit\n" --- 189,196 msgstr " -Z 0-9 nível de compressão para formatos comprimidos\n" #: pg_dump.c:675 pg_dumpall.c:238 pg_restore.c:396 ! msgid " --help show this help, then exit\n" ! msgstr " --help mostra essa ajuda, e termina\n" #: pg_dump.c:676 pg_dumpall.c:239 pg_restore.c:397 msgid " --versionoutput version information, then exit\n" *** src/interfaces/libpq/Makefile~ Fri Dec 13 23:18:22 2002 --- src/interfaces/libpq/Makefile Fri Feb 7 08:47:47 2003 *** *** 29,35 # Add libraries that libpq depends (or might depend) on into the # shared library link. (The order in which you list them here doesn't # matter.) ! SHLIB_LINK += $(filter -lcrypt -ldes -lkrb -lcom_err -lcrypto -lk5crypto -lkrb5 -lssl -lsocket -lnsl -lresolv -lintl, $(LIBS)) all: all-lib --- 29,35 # Add libraries that libpq depends (or might depend) on into the # shared library link. (The order in which you list them here doesn't # matter.) ! SHLIB_LINK += $(filter -lcrypt -ldes -lkrb -lcom_err -lcrypto -lk5crypto -lkrb5 -lssl -lsocket -lnsl -lresolv -lintl -lutil -lasn1 -lroken, $(LIBS)) all: all-lib -- Tom Ivar Helbekkmo, Senior System Administrator, EUnet Norway www.eunet.no T: +47-22092958 M: +47-93013940 F: +47-22092901 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
