Re: [DOCS] [HACKERS] initdb should create a warning message [was Re:
On Sun, 2003-11-30 at 23:18, Neil Conway wrote: > Oliver Elphick <[EMAIL PROTECTED]> writes: > > The use of the word "log" in the directory name does tend to invite > > this error, and some have acted on it without asking first. I think > > initdb should put a README.IMPORTANT file in $PGDATA to say [...] > > If someone deletes something from $PGDATA without understanding what > it is, they deserve what they get. People have a distressing tendency to want to shoot themselves in the foot; and the somewhat unfortunate naming of those files contributes to the problem. While it is satisfying to see stupidity properly rewarded, it is more neighbourly at least to attempt to protect a fool from his folly. It is also kinder to those who may be depending on him for the protection of their data. > I do agree that we could stand to document the purpose of pg_clog > and pg_xlog more clearly. However, this information belongs in the > standard documentation, not scattered throughout $PGDATA. Then it needs to be stated very prominently. But the place to put a sign saying "Dangerous cliff edge" is beside the path that leads along it. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "Who is like unto thee, O LORD, among the gods? who is like thee, glorious in holiness, fearful in praises, doing wonders?" Exodus 15:11 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[DOCS] $BL$>5Bz9-9p!v#22/!"#32/!"#52/(B$B#9@iK|1_<}F~
$BL$>5Bz9-9p!v#22/!"#32/!"#52/[EMAIL PROTECTED]|1_<}F~Z6(2q(B $B;3CfH~Jf$H?=$7$^$9!#(B
$B(B
$BG[?.Dd;_$OBgJQ62=L$G$9$,(B
(Bhttp://www.hosyou.net/cgi-bin/postmail/teishi.html
$B$GAw?.$*4j$$?=$7>e$2$^$9!#!!(B
(B
(B *==*==*==***==*$B!!$40';"!!(B*==*==*==**==*==*==*==*$B(B
$B!!(B
$B!!6`7!$N$3$H$H$*;!$7?=$7>e$2$^$9!#(B
$BFMA3$NG[?.!"@Z$K$4MFe$2$^$9!#(B
(B
(B[EMAIL PROTECTED]|1_!"#12/1_!"@'Hs$"$C$?J}$,$H$NJ}!9$K$*Lr$KN)$D:_Bp%S%8%M%9$G$9!#(B
(B
$B#22/!"#32/!"#52/[EMAIL PROTECTED]|1_<}F~Z5r$,$J$1$l$PC/$G$b?.MQ$7$^$;$s!#(B
(B
$B""(,(,Z5r(,(,8+$;$^$9(,(,2?;[EMAIL PROTECTED]>Z5r(,(,""(B
$B!!(B
$B!!El5~9bEy:[H==j$NH=7h=q!/!"#32/!"#52/[EMAIL PROTECTED]|1_<}F~$N(B
$B!!6d9T0uM-?69~$_=q!&J!;c;vL3=j$h$j$NJ]>Z>Z7t;HMQ0MMj=q!&B>(B
(B
$B""(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,""!!(B
$B(B
$B#22/! /!4/[EMAIL
(BPROTECTED]|1_<}F~Z5r3NG'4?7^(B
(B[EMAIL PROTECTED]&I{6H:_Bp9b3[%M%C%H<}F~L\E*$K:GE,$G$9!#(B
(B
$B"(!!;[EMAIL PROTECTED](Bhttp://www.hosyou.net/$B!!$+$i$*4j$$?=$7>e$2$^$9!#(B
$B!!!Z>Z5r$4Mw2<4j$$$^$9!#>Z5r$,9b3[<}F~$N0FFb?M$G$9![(B
$B!!:G8e$^$G$4MwD:$-M-$jFq$&8f:B$$$^$9!#(B
(B
(B
(B---(end of broadcast)---
(BTIP 9: the planner will ignore your desire to choose an index scan if your
(B joining column's datatypes do not match
[DOCS] PostgreSQL 7.4 Documentation - create_trigger.sgml
In file create_trigger.sgml line 25 is written: funcname and in line 36 is written: class="parameter">func and in line 146 is written: func I think it should be func or funcname in all these lines. In line 40 is written: ... either before before the Halley __ Yahoo! Mail: 6MB, anti-spam e antivírus gratuito! Crie sua conta agora: http://mail.yahoo.com.br ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [DOCS] PostgreSQL 7.4 Documentation - create_trigger.sgml
=?iso-8859-1?q?Halley=20Pacheco=20de=20Oliveira?= <[EMAIL PROTECTED]> writes: > [ mistakes in create_trigger.sgml ] Patches applied. Thanks for the report! regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [DOCS] 7.4 official docs : Fonts?
[sNip] > Pretty much, yes. I don't care much about printing html. If I want > to print I figure I'm better off getting a PDF. I prefer to print from PDF also because the formatting is always perfect. Unfortunately this just hasn't been the case with any other format, including HTML, WordPerfect (and those horrid Microsoft Word) documents, and even plain old text files. At least with PDF this problem has been solved. > I just don't want to have to use a color printer. When I'm reading large amounts of text on paper, black text is my preference because so many people just pick the wrong colours (and pretty much everyone has different tastes and expectations in this regard). -- Randolf Richardson - [EMAIL PROTECTED] Vancouver, British Columbia, Canada Please do not eMail me directly when responding to my postings in the newsgroups. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [DOCS] [PATCHES] Numeric version of factorial()
I had to remove the factorial example from the casting docs because
factorial is now defined only for numeric. Would someone take the
attached example and make a new one with a different operator?
Thanks.
---
Gavin Sherry wrote:
> Attached is a patch implementing factorial(), returning numeric. Points to
> note:
>
> 1) arttype is numeric. I thought this was the best way of allowing
> arbitarily large factorials, even though factorial(2^63) is a large
> number. Happy to change to integers if this is overkill.
> 2) since we're accepting numeric arguments, the patch tests for floats. If
> a numeric is passed with non-zero decimal portion, an error is raised
> since (from memory) they are undefined.
> 3) I have not removed factorial([int2|int4|int8]), not their operator
> counterparts since I didn't know what people would want done with these.
> 4) I haven't added any documentation but am happy to once I know if people
> want int or numeric arguments.
>
> Thanks,
>
> Gavin
Content-Description:
[ Attachment, skipping... ]
>
> ---(end of broadcast)---
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to [EMAIL PROTECTED] so that your
> message can get through to the mailing list cleanly
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
Index: doc/src/sgml/typeconv.sgml
===
RCS file: /cvsroot/pgsql-server/doc/src/sgml/typeconv.sgml,v
retrieving revision 1.39
diff -c -c -r1.39 typeconv.sgml
*** doc/src/sgml/typeconv.sgml 29 Nov 2003 19:51:38 - 1.39
--- doc/src/sgml/typeconv.sgml 1 Dec 2003 21:42:04 -
***
*** 437,466
ERROR: "-4.5e500" is out of range for type double precision
-
-
- On the other hand, the postfix operator ! (factorial)
- is defined only for integer data types, not for float8. So, if we
- try a similar case with !, we get:
-
- SELECT '20' ! AS "factorial";
-
- ERROR: operator is not unique: "unknown" !
- HINT: Could not choose a best candidate operator. You may need to add explicit
- type casts.
-
- This happens because the system can't decide which of the several
- possible ! operators should be preferred. We can help
- it out with an explicit cast:
-
- SELECT CAST('20' AS int8) ! AS "factorial";
-
- factorial
- -
- 243290200817664
- (1 row)
-
-
--- 437,442
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Re: [DOCS] [PATCHES] Numeric version of factorial()
Bruce Momjian <[EMAIL PROTECTED]> writes: > I had to remove the factorial example from the casting docs because > factorial is now defined only for numeric. Would someone take the > attached example and make a new one with a different operator? Done. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [DOCS] [HACKERS] initdb should create a warning message [was Re: [ADMIN] Size on Disk]
Oliver Elphick <[EMAIL PROTECTED]> writes: > On Sun, 2003-11-30 at 23:18, Neil Conway wrote: >> I do agree that we could stand to document the purpose of pg_clog >> and pg_xlog more clearly. However, this information belongs in the >> standard documentation, not scattered throughout $PGDATA. > Then it needs to be stated very prominently. But the place to put a > sign saying "Dangerous cliff edge" is beside the path that leads along > it. How about changing the names of those directories? regards, tom lane ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [DOCS] [HACKERS] initdb should create a warning message [was Re: [ADMIN]
Tom Lane wrote: > Oliver Elphick <[EMAIL PROTECTED]> writes: > > On Sun, 2003-11-30 at 23:18, Neil Conway wrote: > >> I do agree that we could stand to document the purpose of pg_clog > >> and pg_xlog more clearly. However, this information belongs in the > >> standard documentation, not scattered throughout $PGDATA. > > > Then it needs to be stated very prominently. But the place to put a > > sign saying "Dangerous cliff edge" is beside the path that leads along > > it. > > How about changing the names of those directories? I thought about that, but what would we call them? We could change xlog to wal, I guess. That might actually be clearer. xlog could become xstatus or xactstatus or just xact. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [DOCS] [HACKERS] initdb should create a warning message [was Re:
Oliver Elphick <[EMAIL PROTECTED]> writes: > The use of the word "log" in the directory name does tend to invite > this error, and some have acted on it without asking first. I think > initdb should put a README.IMPORTANT file in $PGDATA to say [...] If someone deletes something from $PGDATA without understanding what it is, they deserve what they get. I do agree that we could stand to document the purpose of pg_clog and pg_xlog more clearly. However, this information belongs in the standard documentation, not scattered throughout $PGDATA. -Neil ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [DOCS] [HACKERS] initdb should create a warning message [was Re: [ADMIN]
Bruce Momjian wrote: > Tom Lane wrote: > >>Oliver Elphick <[EMAIL PROTECTED]> writes: >> >>>On Sun, 2003-11-30 at 23:18, Neil Conway wrote: >>> I do agree that we could stand to document the purpose of pg_clog and pg_xlog more clearly. However, this information belongs in the standard documentation, not scattered throughout $PGDATA. >> >>>Then it needs to be stated very prominently. But the place to put a >>>sign saying "Dangerous cliff edge" is beside the path that leads along >>>it. >> >>How about changing the names of those directories? > > > I thought about that, but what would we call them? We could change xlog > to wal, I guess. That might actually be clearer. xlog could become > xstatus or xactstatus or just xact. > active_xdata active_cdata Mike Mascari [EMAIL PROTECTED] ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
