pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: speeves <speeves@unt.edu>
Cc: pgsql-docs@postgresql.org
Subject: Re: docs about security
Date: Thu, 18 Oct 2001 10:51:20 -0400 (EDT)
Message-ID: <200110181451.f9IEpKf09886@candle.pha.pa.us> (raw)
In-Reply-To: <d6351bca.0110171022.1cce600@posting.google.com>

> Hi!
> 
> I am resending a plea for some good security docs, or locations
> thereof.  I have been wrestling with security on Postgres for some
> time, and have finally given up for a time.  Is there a chance that
> someone could write a good tutorial, or a chapter in a book, that can
> explain the various aspects of security on Postgres.
> 
> The reason that I am asking, is because I have been trying to see if
> Postgres would/could be a replacement for our 30+ databases(access +
> sql server).  From the understanding that I get from what I read it
> doesn't look like I can do the security scheme that I want.  (I have
> great respect for all of you who are working on a great product, but
> as of now, I can't wrap my brain around your security scheme...:(  )

Well, my book does cover it a little:
	
	http://www.postgresql.org/docs/awbook.html

There is table-level security (GRANT), view-level security, and
database/host access security.

Tell us what you want to do and we can tell you if you can do it with
PostgreSQL.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (3+ messages)  latest in thread

Message-ID: <200110181451.f9IEpKf09886@candle.pha.pa.us>
Permalink:  ../200110181451.f9IEpKf09886@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200110181451.f9IEpKf09886@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: pgman@candle.pha.pa.us, speeves@unt.edu
  Subject: Re: docs about security
  In-Reply-To: <200110181451.f9IEpKf09886@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox