Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL Password Cracker

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, mlw <pgsql(at)mohawksoft(dot)com>,Devrim GUNDUZ <devrim(at)tr(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PostgreSQL Password Cracker
Date: 2003-01-04 01:33:47
Message-ID: 200301040133.h041XlP05033@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > But it is a "sect1" in libpq.  It should be a "sect1" somewhere that
> > makes more sense.
> > ...
> > It doesn't belong in libpq, and it doesn't belong in the Programmer's
> > Guide.
> 
> How could it not belong in libpq?  But you are right that the
> Programmer's Guide seems the wrong place for information that
> is important to end-users.

Some people don't even know libpq exists.  If someone uses only
psql, how would they know?

> Perhaps libpq needs to have a chapter in the User's Guide as
> well as a chapter in the Programmer's Guide?

> Or maybe we could put the relevant information into a reference
> page under PostgreSQL Client Applications (titled something
> along the line of "common behavior of all libpq-based client
> applications").

Yep, that's what I would do.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-01-04 01:34:02
Subject: Re: Threads
Previous:From: Lamar OwenDate: 2003-01-04 01:32:15
Subject: Re: Upgrading rant.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group