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

Re: PG vs MySQL

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>,"Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>,Mike Nolan <nolan(at)gw(dot)tssi(dot)com>,"Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>,Alex <alex(at)meerkatsoft(dot)com>, Frank Finner <postgresql(at)finner(dot)de>,pgsql-general(at)postgresql(dot)org
Subject: Re: PG vs MySQL
Date: 2004-03-29 23:12:28
Message-ID: 20040329191036.Y51637@ganymede.hub.org (view raw or flat)
Thread:
Lists: pgsql-general
On Mon, 29 Mar 2004, Tom Lane wrote:

> It might be possible to do something with a flat file as an intermediary
> between the postmaster and the tables that are the master data.  We
> already do this for pg_shadow passwords, and I've been thinking of
> proposing that we add a flat file for the database name -> OID mapping
> so we could get rid of the horrid hack that is GetRawDatabaseInfo().
> Per-database flat files would be a bit messy though.

The ability to manipulate pg_hba via interfaces stuck as phpPgAdmin and
PgAdmin would definitely be a plus, even if it just results in something
like pg_shadow ... in an ISP environment, pg_hba is about the only
'hassle' that I think really exists ...

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org           Yahoo!: yscrappy              ICQ: 7615664

In response to

pgsql-general by date

Next:From: Mike NolanDate: 2004-03-30 00:16:03
Subject: Re: PG vs MySQL
Previous:From: Marc G. FournierDate: 2004-03-29 23:06:43
Subject: Re: PG vs MySQL

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