Marko Kreen <[EMAIL PROTECTED]> writes:
> Another idea is stop storing hashes altogether
You can already avoid passwords by using kerberos authentication.
--
Trond Eivind Glomsrød
Red Hat, Inc.
---(end of broadcast)---
TIP 2: you can get off all
On Fri, 28 Sep 2001, Dinesh Parikh wrote:
> Dear All,
> I am new in postgres there for i have some problems. I am executing
> some type of Business rule in strored procedure using language
> plpgsql. When I am executing a Dynamic Query then It return an error
> which is some how unable to under
Hi all,
Database: 7.1.3 (RPM)
OS: Redhat 7.1
Table: Create table jquserdata (
Username
varchar(20)
not null, primary key,
…)
Copy some corrupted data
from a 7.1.3 (Encoding ASCII) with pg_
IIRC, any things where you're doing creates/drops
in plpgsql pretty much mean you have to generate
the statements as strings and use EXECUTE which
will prevent the plans from being cached.
On Fri, 28 Sep 2001, Dinesh Parikh wrote:
> Dear all, I have a strange problem.Document says that one can
Do you mean, not deleted "ever" or not when you expect them to be? If you
are using persistent connections in PHP, the table will remain until the
Apache process that possesses the connection is destroyed, or you
specifically destroy the table.
Keary Suska
Esoteritech, Inc.
"Leveraging Open Sourc
> I have a problem at the time of requete containing accents with
> PostgreSQL version 6.5.3 :
>
> Via psql, the following requete does not function :
>
> SELECT id_dico, name
> FROM dico_fr
> WHERE name ~* '^bé'
> ORDER BY name;
>
>
> The tables are coded in UNICODE.
Are you sure t
yes, vacuum analyze is used constantly.
--Ben
--- Fernando Schapachnik <[EMAIL PROTECTED]>
> wrote:
>Have you vacuum analyzed after the restore?
>
>En un mensaje anterior, Benjamin Franks escribi=F3:
>> I have a dual-CPU (PIII 600MHz), 512MB, IDE-HD box. A couple of months a=
>go I was using Lin
