Re: Default privileges for new databases (was Re: Can't import large objects in most recent cvs)

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ron Snyder <snyder(at)roguewave(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Default privileges for new databases (was Re: Can't import large objects in most recent cvs)
Date: 2002-06-18 00:10:02
Message-ID: 200206171710.02043.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Folks,

> Adding too many options to initdb is not a path I would prefer since
> initdb happens mostly hidden from the user these days.

What about adding a parameter to CREATE DATABASE, then? Like CREATE DATABASE
db1 WITH (SECURE)?

--
-Josh Berkus

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-06-18 01:00:46 Re: Roadmap for a Win32 port
Previous Message Hiroshi Inoue 2002-06-17 23:59:28 Re: SetQuerySnapshot, once again