Re: BUG #13589: content error - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #13589: content error
Date
Msg-id 1637.1442377612@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #13589: content error  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: BUG #13589: content error  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
Thomas Munro <thomas.munro@enterprisedb.com> writes:
> Thanks for taking a look at this.  I don't want my attempt to steer things
> in a more conservative direction to result in the original complaint not
> being fixed, so how about considering just this change to start.sgml for
> now:

>     <para>
>      Possibly, your site administrator has already created a database
> -    for your use.  He should have told you what the name of your
> +    for your use and told you what the name of your
>      database is.  In that case you can omit this step and skip ahead
>      to the next section.
>     </para>

That would work, but I still wonder why we need that second sentence
at all.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #13589: content error
Next
From: Tazhkenov Denis
Date:
Subject: JDBC driver setNull(_,Types.OTHER) bug