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 = CURR
-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 PostgreS
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
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
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 vers
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 neces
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.
C
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 doin
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 Mar
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
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 lis
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 bac
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 li
13 matches
Mail list logo
