Re: 21.3 Template database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dmitry Igrishin <dmitigr(at)gmail(dot)com>
Cc: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: 21.3 Template database
Date: 2015-08-04 14:18:39
Message-ID: 24976.1438697919@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Dmitry Igrishin <dmitigr(at)gmail(dot)com> writes:
> The sentence of 2nd paragraph says:
> "This is particularly handy when restoring a pg_dump dump"
> I suggest to add apostrophe:
> "This is particularly handy when restoring a pg_dump's dump"

> The sentece of 5th paragraph says:
> "The principal limitation is that no other sessions can be connected
> to the source database while it is being copied. CREATE
> DATABASE will fail if any other connection exists when it starts;
> during the copy operation, new connections to the source database are
> prevented."
> I suggest to get rid from redundant phrase:
> "The principal limitation is that no other sessions can be connected to the
> source database while it is being copied and CREATE DATABASE will fail if
> any other connection exists when it starts."

TBH, both of those seem to read worse to me than what's there now.

regards, tom lane

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Dmitry Igrishin 2015-08-04 15:45:53 25.1. Comparison of Different Solutions
Previous Message Dmitry Igrishin 2015-08-04 13:15:47 21.3 Template database