> Greetings.
>
> Using pg6.5.1 on Solaris 2.6, I'm trying to create a very simple function
> using plpgsql. Here's the code I've executed:
>
> /*
> CREATE FUNCTION plpgsql_call_handler () RETURNS OPAQUE AS
> '/opt/pgsql/lib/plpgsql.so' LANGUAGE 'C';
>
> CREATE TRUSTED PROCEDURAL LANGUAGE
Try to replace the following:
return t;
by return ''t'';
and return f; by return ''f'';
It's not a double quote but a quote quote :-)
-Message d'origine-
De: Andrew Perrin - Demography [SMTP:[EMAIL PROTECTED]]
Date: mercredi 3 novembre 1999 07:18
A: [EMAIL PROTECTED]
Objet
On Fri, 05 Nov 1999, you wrote:
> Ah, your description just tripped a memory for me from the hackers list:
>
> The behavior you describe has to do with the implementation of using an
> index for regex matching, in the presence of the USE_LOCALE configuration
> option.
>
> Internally, the conditi
Ah, your description just tripped a memory for me from the hackers list:
The behavior you describe has to do with the implementation of using an
index for regex matching, in the presence of the USE_LOCALE configuration
option.
Internally, the condition: WHERE word~'^alongword' is converted in th
On Fri, 05 Nov 1999, Gene Selkov, Jr. wrote:
> OK, let's turn from speculations to facts (have just gotten off my
> rear end and verified each).:
>
> 1. '^whatever.*' and '^whatever' are equivalent regular expressions.
yes, sorry, I was aware of this, although I was using .* for clarity and my
m
Hi,
I'm using postgresql 6.5.1 on RH6.0 and can't do a
select during atransaction. Is there a reason for this
behavior?
Here is a simplified example:
psql wwmixWelcome to the POSTGRESQL interactive
sql monitor: Please read the file COPYRIGHT for copyright terms of
POSTGRESQL[PostgreSQ
> > unfortunately '^whatever.*' is what I'm trying to locate (ie: all words
> > starting with whatever, but with nay trailing text), the problem seems to be in
> > the termination of the index scan, not in the actual regex match (which actually
> > seems very good, speed wise..) otherwise I could
Bruce Momjian wrote:
> Very strange. Same postmaster flags? I can't imagine what it would be?
> We really have been improving performance, including startup
> performance.
The only difference I see is -i flag on the 6.5 postmaster, but removing it
doesn't change a thing, connecting is consiste
On Thu, 4 Nov 1999, Stuart Woolford wrote:
> unfortunately '^whatever.*' is what I'm trying to locate (ie: all words
> starting with whatever, but with nay trailing text), the problem seems to be in
> the termination of the index scan, not in the actual regex match (which actually
> seems very go
On Thu, 04 Nov 1999, Gene Selkov, Jr. wrote:
> > select key from inv_word_i where word='whatever' order by count desc ;
> >
> > and this is fast, however, if I use:
> >
> > select key from inv_word_i where word~'^whatever.*' order by count desc ;
> >
> > it is very slow.
>
> Did you try '^what
By the way,
I've created a secondary index on a large table in order to
gain some speed (the index is not unique), but the "explain"
did not report any change.
What else do I have to do to actually *use* an index? The manual
only tells how to create one.
FAQ?
Regards,
Holger Klawitte
On Thu, 4 Nov 1999 [EMAIL PROTECTED] wrote:
> > CREATE USER sql command updates the file, but an UPDATE on pg_shadow
> > does not.
>
> IMHO, that's a bug:
> It's not forbidden to update or insert into pg_shadow by rule, but if
> I do that I will get inconsistent authentication data.
> Why not re
12 matches
Mail list logo
