Re: create database with template doesn't copy database ACL

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Joseph Nahmias <joe(at)nahmias(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: create database with template doesn't copy database ACL
Date: 2020-06-15 14:10:32
Message-ID: 20200615141032.GC12121@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On Mon, Jun 15, 2020 at 12:14:55AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Well, I thought we copied everything except things tha can be specified
> > as different in CREATE DATABASE, though I can see why we would not copy
> > them. Should we document this or issue a notice about not copying
> > non-default database attributes?
>
> We do not need a notice for behavior that (a) has stood for twenty years
> or so, and (b) is considerably less broken than any alternative would be.
> If you feel the docs need improvement, have at that.

Well, I realize it has been this way for a long time, and that no one
else has complained, but there should be a way for people to know what
is being copied from the template and what is not. Do we have a clear
description of what is copied and skipped?

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com

The usefulness of a cup is in its emptiness, Bruce Lee

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2020-06-16 07:10:56 Regarding query sort order for "select distinct"
Previous Message Tom Lane 2020-06-15 04:14:55 Re: create database with template doesn't copy database ACL

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Sharma 2020-06-15 14:11:03 Re: Parallel copy
Previous Message Tom Lane 2020-06-15 13:59:21 Re: factorial of negative numbers