Re: [BUGS] Documentation bug regarding collations

2012-01-28 Thread Tom Lane
Thomas Kellerer writes: > in the description of the ORDER BY clause > (http://www.postgresql.org/docs/current/static/sql-select.html#SQL-ORDERBY) > it says: > "Character-string data is sorted according to the locale-specific collation > order that was established when the database was created."

[BUGS] Documentation bug regarding collations

2012-01-28 Thread Thomas Kellerer
in the description of the ORDER BY clause (http://www.postgresql.org/docs/current/static/sql-select.html#SQL-ORDERBY) it says: "Character-string data is sorted according to the locale-specific collation order that was established when the database was created." Which is no longer true with 9.

Re: [BUGS] Documentation bug: reference to checkpoint activity in bgwriter

2012-01-19 Thread Peter Geoghegan
On 20 January 2012 02:53, Robert Haas wrote: > OK, done. Thanks -- Peter Geoghegan       http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training and Services -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.po

Re: [BUGS] Documentation bug: reference to checkpoint activity in bgwriter

2012-01-19 Thread Robert Haas
On Mon, Jan 9, 2012 at 2:37 PM, Peter Geoghegan wrote: > On 9 January 2012 18:47, Robert Haas wrote: >> On Sat, Dec 31, 2011 at 8:54 PM, Peter Geoghegan >> wrote: >>> ISTM that the following reference, at config.sgml line 1345, ought to >>> be adjusted due to the introduction of the new checkpo

Re: [BUGS] Documentation bug: reference to checkpoint activity in bgwriter

2012-01-09 Thread Peter Geoghegan
On 9 January 2012 18:47, Robert Haas wrote: > On Sat, Dec 31, 2011 at 8:54 PM, Peter Geoghegan > wrote: >> ISTM that the following reference, at config.sgml line 1345, ought to >> be adjusted due to the introduction of the new checkpointer process: >> >>  Setting this to zero disables >>        

Re: [BUGS] Documentation bug: reference to checkpoint activity in bgwriter

2012-01-09 Thread Robert Haas
On Sat, Dec 31, 2011 at 8:54 PM, Peter Geoghegan wrote: > ISTM that the following reference, at config.sgml line 1345, ought to > be adjusted due to the introduction of the new checkpointer process: > >  Setting this to zero disables >         background writing (except for checkpoint activity).

[BUGS] Documentation bug: reference to checkpoint activity in bgwriter

2011-12-31 Thread Peter Geoghegan
ISTM that the following reference, at config.sgml line 1345, ought to be adjusted due to the introduction of the new checkpointer process: Setting this to zero disables background writing (except for checkpoint activity). -- Peter Geoghegan       http://www.2ndQuadrant.com/ PostgreSQL

Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers

2011-05-05 Thread Josh Kupershmidt
[Moving to -docs] On Mon, May 2, 2011 at 12:00 PM, Pavel Stehule wrote: > Hello > > one czech user reported a bug in documentation - > http://www.postgresql.org/docs/8.4/static/plpgsql-trigger.html > > NEW > >    Data type RECORD; variable holding the new database row for > INSERT/UPDATE operatio

[BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers

2011-05-02 Thread Pavel Stehule
Hello one czech user reported a bug in documentation - http://www.postgresql.org/docs/8.4/static/plpgsql-trigger.html NEW Data type RECORD; variable holding the new database row for INSERT/UPDATE operations in row-level triggers. This variable is NULL in statement-level triggers and for DELE

Re: [BUGS] Documentation bug: Chapter 35.4, paragraph 4

2011-03-10 Thread Bruce Momjian
Robert Haas wrote: > On Tue, Nov 23, 2010 at 1:08 PM, Jonathan Pool wrote: > > Chapter 35.4, paragraph 4, of the PostgreSQL 9.0.1 Documentation says: > > > > Any collection of commands in the SQL language can be packaged together and > > defined as a function. Besides SELECT queries, the commands

Re: [BUGS] Documentation bug: Chapter 35.4, paragraph 4

2011-03-10 Thread Jonathan Pool
> I just made the wording more generic Thanks much. ˉ -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] Documentation bug: Chapter 35.4, paragraph 4

2010-11-28 Thread Robert Haas
On Tue, Nov 23, 2010 at 1:08 PM, Jonathan Pool wrote: > Chapter 35.4, paragraph 4, of the PostgreSQL 9.0.1 Documentation says: > > Any collection of commands in the SQL language can be packaged together and > defined as a function. Besides SELECT queries, the commands can include data > modifica

[BUGS] Documentation bug: Chapter 35.4, paragraph 4

2010-11-23 Thread Jonathan Pool
Chapter 35.4, paragraph 4, of the PostgreSQL 9.0.1 Documentation says: Any collection of commands in the SQL language can be packaged together and defined as a function. Besides SELECT queries, the commands can include data modification queries (INSERT, UPDATE, and DELETE), as well as other SQL

Re: [BUGS] Documentation Bug related to Inheritance

2001-07-23 Thread Felipe Alvarez Harnecker
Tom Lane writes: > >> Well, beside the referential constraint issue ( that can be solved by > >> hand ), the most frustrating is that queries like > >> DELETE FROM table* where key = some_value > >> Fails ( parser error ). ( UPDATE either ) > > Not as of 7.1. > > re

Re: [BUGS] Documentation Bug related to Inheritance

2001-07-20 Thread Tom Lane
>> Well, beside the referential constraint issue ( that can be solved by >> hand ), the most frustrating is that queries like >> DELETE FROM table* where key = some_value >> Fails ( parser error ). ( UPDATE either ) Not as of 7.1. regards, tom lane -

Re: [BUGS] Documentation Bug related to Inheritance

2001-07-20 Thread Bruce Momjian
> > Hi, i've posted various problems regarding inheritance in postgres, > Never see a reply :( > > Well, beside the referential constraint issue ( that can be solved by > hand ), the most frustrating is that queries like > > DELETE FROM table* where key = some_value > > Fails ( parser error )

[BUGS] Documentation Bug related to Inheritance

2001-07-20 Thread Felipe Alvarez Harnecker
Hi, i've posted various problems regarding inheritance in postgres, Never see a reply :( Well, beside the referential constraint issue ( that can be solved by hand ), the most frustrating is that queries like DELETE FROM table* where key = some_value Fails ( parser error ). ( UPDATE either )

[BUGS] Documentation Bug related to Inheritance

2001-07-20 Thread Danilo Gonzalez Hashimoto
Inheritance is one of the most useful and 'marketed' features in PostgreSQL. However its behavior is not what one expected it to be. Inherited tables do not inherit some constraints, including primary and foreing keys. This information is very important, specially for newbies, who can get very f

Re: [BUGS] Documentation bug for pg_ctl (-s option not documented)

2001-05-03 Thread Bruce Momjian
This is fixed in 7.1.1. > Hello: > > In version 7.1 the man page for pg_ctl does not document -s option. > > Thanks, > -- > Arcady Genkin > > ---(end of broadcast)--- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/u

[BUGS] Documentation bug for pg_ctl (-s option not documented)

2001-05-03 Thread antipode
Hello: In version 7.1 the man page for pg_ctl does not document -s option. Thanks, -- Arcady Genkin ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html

Re: [BUGS] Documentation bug

2000-09-27 Thread Bruce Momjian
Thanks. Fixed. > Marius Kintel ([EMAIL PROTECTED]) reports a bug with a severity of 4 > The lower the number the more severe it is. > > Short Description > Documentation bug > > Long Description > in file "user/app-psql.htm" > > \copy table [ with oids ] { from | to } filename | stdin | stdou

[BUGS] Documentation bug

2000-09-27 Thread pgsql-bugs
Marius Kintel ([EMAIL PROTECTED]) reports a bug with a severity of 4 The lower the number the more severe it is. Short Description Documentation bug Long Description in file "user/app-psql.htm" \copy table [ with oids ] { from | to } filename | stdin | stdout [ with delimiters 'characters' ] [