Hello,
since I upgraded PostgreSQL it now stores passwords in MD5 format. When
I try connecting using password authentication, i get:
Jan 9 12:22:24 prometheus postgres[28540]: [2] LOG: Password is stored
MD5 encrypted. 'password' and 'crypt' auth methods cannot be used.
Now, if password and
The recommendation is to use MD5. However, 7.3.1 has a fix so you can
use 'password' again.
---
Peter Schuller wrote:
> Hello,
>
> since I upgraded PostgreSQL it now stores passwords in MD5 format. When
> I try connecting
On Mon, 23 Dec 2002 10:41:31 -0500, Timothy D McKernan wrote:
> Before we push it out into our production environment I wanted to make
> one last check with regards to bugs - is anybody aware of any bugs that
> have popped up in 7.3? I haven't seen any unexpected issues on the
> mailing lists but
Would you grab the CVS and give it a try. I want to put out a new
release shortly anyway.
---
Jeff Boes wrote:
> On Mon, 23 Dec 2002 10:41:31 -0500, Timothy D McKernan wrote:
>
> > Before we push it out into our production
I work with the
SGBDR OpenIngres2 which has also a WAL mecanism.More over, I journalise my
database in order to recover the data between thesave of the data and the
crash.Is it possible to do it with PostgreSQL
?thanks
> The recommendation is to use MD5. However, 7.3.1 has a fix so you can
> use 'password' again.
Ok - thanks!
--
/ Peter Schuller, InfiDyne Technologies HB
PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>'
Key retrival: Send an E-Mail to [EMAIL PROTECTED]
E-Mail: [EMAIL PROTECTED]
On Fri, 03 Jan 2003 10:19:44 -0500, David F. Skoll wrote:
> Is there any way to adaptively vacuum the database? By this, I mean is
> it possible to run a query every few minutes and decide to vacuum based
> on the query results?
You may want to investigate this:
http://gborg.postgresql.org/proj
