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."
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.
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
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
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
>>
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).
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
[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
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
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
> 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
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
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
http://wwwmaster.postgresql.org/commentdoc
Internal Server Error
Error communicating with database: ERROR: invalid input syntax for type
numeric: ""
Privacy Policy | Project hosted by our server sponsors. | Designed by tinysofa
Copyright © 1996 - 2008 PostgreSQL Global Development Group
The pa
karol dzięgielewski написа:
> Hi,
> Where can I find documentation in pdf format?
> Regards Karol Dzięgielewski
That's not a bug.
http://www.postgresql.org/docs/manuals/
--
Milen A. Radev
---(end of broadcast)---
TIP 4: Have you searched our l
karol dzięgielewski wrote:
> Hi,
> Where can I find documentation in pdf format?
http://www.postgresql.org/docs/manuals/
//Magnus
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Hi,
Where can I find documentation in pdf format?
Regards Karol Dzięgielewski
Maxim Britov <[EMAIL PROTECTED]> writes:
> maxim=# SELECT version()
> maxim-# SELECT version();
> ERROR: syntax error at or near "SELECT" at character 18
> СТРÐÐÐ 2: SELECT version();
> ^
What you typed there was a two-line query equivalent to
SELECT version() SELECT versi
I read it http://www.postgresql.org/docs/8.1/interactive/tutorial-accessdb.html
I can't use examples:
maxim-# SELECT version();
ERROR: syntax error at or near "SELECT" at character 18
СТРОКА 2: SELECT version();
^
maxim=# SELECT version() ;
On Wed, 1 Nov 2006 15:57:22 +0200
Maxim Britov wrote:
> I read it
> http://www.postgresql.org/docs/8.1/interactive/tutorial-accessdb.html
>
> I can't use examples:
Sorry, my I know my mistake now. :)
--
Maxim Britov
GnuPG KeyID 0x4580A6D66F3DB1FB xmpp:[EMAIL PROTECTED] icq 198171258
Finger
Patch applied. Thanks.
---
Andrew McMillan wrote:
> On Wed, 2002-05-29 at 01:41, Tom Lane wrote:
> >
> > > Is it a good idea to provide an example (such as the above), or should I
> > > just try and describe the behavi
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Andrew McMillan wrote:
> On Wed, 2002-05-29 at
On Wed, 2002-05-29 at 01:41, Tom Lane wrote:
>
> > Is it a good idea to provide an example (such as the above), or should I
> > just try and describe the behaviour?
>
> Examples are generally good things ...
OK, the attached documentation patch provides some simple examples of
use of tablename
Andrew McMillan <[EMAIL PROTECTED]> writes:
> ... I can't supply either %ROWTYPE or %TYPE within the parameter
> definition without an error either.
Looks like I was mistaken: table.field%type works, but table%type
does not:
test72=# create table foo (f1 int, f2 text);
CREATE
test72=# create fun
On Tue, 2002-05-28 at 04:59, Tom Lane wrote:
> Andrew McMillan <[EMAIL PROTECTED]> writes:
> > Reading between a few lines I got the impression that the manual
> > suggested something like:
> > CREATE or REPLACE myfunc( tablename%ROWTYPE ) RETURNS ...
> > When I finally got my function working, I
Andrew McMillan <[EMAIL PROTECTED]> writes:
> Reading between a few lines I got the impression that the manual
> suggested something like:
> CREATE or REPLACE myfunc( tablename%ROWTYPE ) RETURNS ...
> When I finally got my function working, I found I had:
> CREATE or REPLACE myfunc( tablename ) RE
I recently referred to the manual (section 23.3) to work out how to
write a PL/PgSQL function that accepted a row as a parameter.
Reading between a few lines I got the impression that the manual
suggested something like:
CREATE or REPLACE myfunc( tablename%ROWTYPE ) RETURNS ...
When I finally g
[EMAIL PROTECTED] writes:
> Section 3.3, tutorial-fk.html
> You have written 'references weather' instead of 'references cities'.
This seems to be fixed already.
> Line 9 refers to 'advanced' instead of 'syscat' in syscat.py
Good catch, thanks for the report!
regards,
Hi,
Section 3.3, tutorial-fk.html
CREATE TABLE cities (
namevarchar(80) primary key,
locationpoint
);
CREATE TABLE weather (
cityvarchar(80) references weather,
temp_lo int,
temp_hi int,
prcp
Rich Morin writes:
> It is a ToC entry, looking like
>
>"12.1.7. The #random# test ... 76"
>
> where the '#'s actually show up as squares.
Those are supposed to be double quotes. It's possible that the
Microsoftish "smart quotes" snuck in here. We'll be alert next time
around.
--
Peter
The peculiar codes (\223, \224) appear to be "character codes", but
not ones that seem very standardized. The "PostScript Language
Reference Manual" (2nd Ed.) gives the following information:
"E.6 StandardEncoding Encoding Vector", p. 598
"E.9 Expert Encoding Vector", p. 602
At 5:13 PM +0100 11/15/01, Peter Eisentraut wrote:
>Rich Morin writes:
>
>> PostreSQL 7.1 Administrator's Guide
>>
>> On page iii (2nd line), something is printing as a square (?).
>
>Could you give some context? I don't have the specific document at hand.
It is a ToC entry, looking like
Rich Morin writes:
> PostreSQL 7.1 Administrator's Guide
>
>On page iii (2nd line), something is printing as a square (?).
Could you give some context? I don't have the specific document at hand.
> PostreSQL 7.1 Developer's Guide
>
>The Arabic page numbers do not match the actual page
>On page xv (antepenultimate line), "Gnu Project" should be "GNU
>Project".
Fixed. Thanks.
>On page 78, the "Release date" is listed as "2001-??-??".
This is a tough one. We generate the docs before we know the date of
final release. Does anyone have a suggestion on how to fix th
I am not a PostgreSQL user, just an editor who has looked over some
of your printable documentation. I found some problems and thought
you'd like to know about them...
-r
PostreSQL 7.1 Administrator's Guide
On page iii (2nd line), something is printing as a square (?).
On page xv (ante
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
>> 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
-
>
> 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 )
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 )
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
My application runs slower than a month of Sundays.
I found, quite by accident, that I need to "Turn off auto-commit."
Nowhere, and I've even resorted to running grep over the documentation,
can I find any cluse as to ahow I "Turn off auto-commit."
I don't understand why I should have to "Tur
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
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
text data type is described as as unlimited length, where it is actually
limited by the size of page block (8k)
Best,
Igor Seletskiy
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/fa
Thanks. Docs updated.
> The programmers guide states that in order to load the JDBC
> driver, you use the class name "postgresql.Driver"
>
> http://www.postgresql.org/users-lounge/docs/7.0/programmer/jdbc6424.htm
>
> This is only true if you compile the driver to use the 1.1
> JDK; if you comp
The programmers guide states that in order to load the JDBC
driver, you use the class name "postgresql.Driver"
http://www.postgresql.org/users-lounge/docs/7.0/programmer/jdbc6424.htm
This is only true if you compile the driver to use the 1.1
JDK; if you compile it to use the 1.2 jdk the class wi
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
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' ] [
48 matches
Mail list logo
