Re: [DOCS] Misleading

2017-04-11 Thread Bruce Momjian
On Wed, Apr 5, 2017 at 12:28:46AM -0400, Peter Eisentraut wrote: > On 3/28/17 07:02, marek.cvo...@gmail.com wrote: > > My suggestion: > > - completely omit confusing default word: > > `You can also specify user and port values, and whether you want the data > > linked instead of copied.` > > It'

Re: [DOCS] Misleading

2017-04-04 Thread Peter Eisentraut
On 3/28/17 07:02, marek.cvo...@gmail.com wrote: > Please correct following part of pg_upgrade documentation: > `You can also specify user and port values, and whether you want the data > linked instead of copied (the default).` > > It is not clear what is the default option. If you read the whole

Re: [DOCS] misleading ALTER TABLE SET STORAGE

2016-11-10 Thread Tom Lane
Euler Taveira writes: > On 08-11-2016 11:27, vode...@gmail.com wrote: >> Was reading >> https://www.postgresql.org/docs/current/static/storage-toast.html and the >> bit with "...table column can be altered with ALTER TABLE SET >> STORAGE..." >> appeared misleading to me. > AFAICS ALTER TABLE SET

Re: [DOCS] misleading ALTER TABLE SET STORAGE

2016-11-10 Thread Euler Taveira
On 08-11-2016 11:27, vode...@gmail.com wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/storage-toast.html > Description: > > Hi, > Was reading > https://www.postgresql.org/docs/current/static/storage-toast.html and

Re: [DOCS] Misleading text mesage

2016-06-13 Thread Peter Eisentraut
On 6/7/16 2:57 AM, javier.diaz.s...@gmail.com wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/7.4/static/jdbc-query.html Description: In https://www.postgresql.org/docs/7.4/static/jdbc-query.html System.out.print("Column 1 returne

Re: [DOCS] misleading lang_name case in CREATE FUNCTION doc.

2014-02-13 Thread Bruce Momjian
On Tue, Nov 26, 2013 at 07:28:17PM +, Marc Mamin wrote: > > >Von: Peter Eisentraut [pete...@gmx.net] > > >>On 11/13/13, 9:02 AM, Marc Mamin wrote: > >> something like :? > >> > >> The name of the language that the function is implemented in. > >> Can be 'sql', 'c', 'internal', or the name of

Re: [DOCS] misleading lang_name case in CREATE FUNCTION doc.

2013-11-30 Thread Marc Mamin
>Von: Peter Eisentraut [pete...@gmx.net] >>On 11/13/13, 9:02 AM, Marc Mamin wrote: >> something like :? >> >> The name of the language that the function is implemented in. >> Can be 'sql', 'c', 'internal', or the name of a user-defined procedural >> language. >> Single quotes are optional, they

Re: [DOCS] misleading lang_name case in CREATE FUNCTION doc.

2013-11-26 Thread Peter Eisentraut
On 11/13/13, 9:02 AM, Marc Mamin wrote: > something like :? > > The name of the language that the function is implemented in. > Can be 'sql', 'c', 'internal', or the name of a user-defined procedural > language. > Single quotes are optional, they required correct case when used. That would mak

Re: [DOCS] misleading lang_name case in CREATE FUNCTION doc.

2013-11-15 Thread Marc Mamin
> From: Peter Eisentraut [mailto:pete...@gmx.net] > Sent: Mittwoch, 13. November 2013 12:56 > On Fri, 2013-10-11 at 08:37 +, Marc Mamin wrote: > > Hi, > > you might want to lowercase the language names in order to be > > compatible with the case restriction introduced in 9.2. > > or add a

Re: [DOCS] misleading lang_name case in CREATE FUNCTION doc.

2013-11-13 Thread Peter Eisentraut
On Fri, 2013-10-11 at 08:37 +, Marc Mamin wrote: > Hi, > you might want to lowercase the language names in order to be > compatible with the case restriction introduced in 9.2. > or add a sentence like > 'when using single quotes, the names are case sensitive (with is > lowercase for most (al