| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | shurutov(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16214: Settings is not copy |
| Date: | 2020-01-17 05:37:55 |
| Message-ID: | 4217.1579239475@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> Than I made copy as "CREATE DATABASE demo_small template demo", after this I
> noticed:
> ...
> Parameter "search_path" was not copied.
CREATE DATABASE is not defined to copy database-level properties,
only the contents of the database. As it says in the manual,
this is not really intended as a general-purpose database copying
command in the first place. For its intended purpose, copying
database-level properties wouldn't be particularly desirable.
Certainly you wouldn't want it to clone the database's ownership
or ACL.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-01-17 06:29:45 | Re: libpq parameter parsing problem |
| Previous Message | Tom Lane | 2020-01-17 04:30:03 | Re: SQL/PostgreSQL - Error observed in the QUERY not caught by the “EXCEPTION” block in the stored procedure |