Re: [DOCS] Automatic documentation spell check
Peter Eisentraut wrote: > I've installed an automatic spell-checker for the documentation. You can > see the results at > > http://developer.postgresql.org/docs/postgres/spell-check.txt > > It updates every time the documentation updates. > > Obviously, it's not perfect, but I've found it quite useful over time. In > fact, you'll see a couple of genuine misspellings right in this run. Should we list this URL on the developer's page where we list the doc builds? -- 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 4: Don't 'kill -9' the postmaster
Re: [DOCS] [HACKERS] What goes into the security doc?
I've started. I'm wondering how much we need to cover here and how much can be delegated to other sections of the documentation. Before I get very far into this, I want to get some ideas as to what we need. This is what I have so far: http://www.freebsddiary.org/tmp/PostgreSQL-security.txt cheers On 16 Aug 2003 at 12:41, Bruce Momjian wrote: > > Now that we are in beta, does someone want to tackle a "security" > section in the docs? > > > --- > > Dan Langille wrote: > > With reference to my post to the "PostgreSQL Password Cracker" on > > 2003-01-02, I've promised to write a security document for the project. > > Here it is, Sunday night, and I can't sleep. What better way to get there > > than start this task... > > > > My plan is to write this in very simple HTML. I will post the draft > > document on my website and post the URL here from time to time for > > feedback. Please make suggestions for content. So far, I will cover these > > items: > > > > - .pgpass (see > > http://developer.postgresql.org/docs/postgres/libpq-files.html) > > - local connections > > - remote connections (recommending SSL) > > - pg_hba (only in passing, most of that is at > > http://www.postgresql.org/idocs/index.php?client-authentication.html) > > - running the postmaster as a specific user > > > > That doesn't sound like much. Surely you can think of something else to > > add. Should I post this to another list for their views? > > > > OK, that's done it. I'm ready for sleep now. > > > > > > ---(end of broadcast)--- > > TIP 5: Have you checked our extensive FAQ? > > > > http://www.postgresql.org/users-lounge/docs/faq.html > > > > -- > 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 > -- Dan Langille : http://www.langille.org/ ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [DOCS] [HACKERS] What goes into the security doc?
Dan Langille writes: > I've started. I'm wondering how much we need to cover here and how > much can be delegated to other sections of the documentation. Before > I get very far into this, I want to get some ideas as to what we > need. If you intend this to go into the main documentation, then I think we don't need anything, because everything is already documented in its proper place. What you wrote is basically just a summary of various system aspects that might have to do with that vague word "security", together with pointers to the places where they are documented (which reinforces my point). Perhaps a "howto" format that you can post on techdocs might be more appropriate for you. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [DOCS] [HACKERS] What goes into the security doc?
On 30 Aug 2003 at 16:15, Peter Eisentraut wrote: > Dan Langille writes: > > > I've started. I'm wondering how much we need to cover here and how > > much can be delegated to other sections of the documentation. Before > > I get very far into this, I want to get some ideas as to what we > > need. > > If you intend this to go into the main documentation, then I think we > don't need anything, because everything is already documented in its > proper place. It has already been decided that we need something. Hence the request for someone to write it and my start on the task. > What you wrote is basically just a summary of various > system aspects that might have to do with that vague word "security", > together with pointers to the places where they are documented (which > reinforces my point). Your point being that we don't need anything more than we already have? That conflicts with what has already been decided. > Perhaps a "howto" format that you can post on > techdocs might be more appropriate for you. I'm not sure what you mean by "for you". -- Dan Langille : http://www.langille.org/ ---(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] PostgreSQL Tutorial in Russian
Viktor Vislobokov wrote: > Hello Bruce! > > > I finished first version of my own translation of PostgreSQL Tutorial > (for PostgreSQL 7.3.3). > The translation is not fully nice, but I think, it ready for use. > > I ask to help Oleg Bartunov and he is began read and fix some > things, but then he say, he has no time, because he works for > preparing next version of PostgreSQL. > > I can send translated sgml to you. Do you want this? [ CC'ing docs list.] I am not sure how we handle translations of the docs. Folks? -- 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 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [DOCS] PostgreSQL Tutorial in Russian
Le Samedi 30 Août 2003 14:33, Bruce Momjian a écrit : > Viktor Vislobokov wrote: > > Hello Bruce! > > > > > > I finished first version of my own translation of PostgreSQL Tutorial > > (for PostgreSQL 7.3.3). > > The translation is not fully nice, but I think, it ready for use. > > > > I ask to help Oleg Bartunov and he is began read and fix some > > things, but then he say, he has no time, because he works for > > preparing next version of PostgreSQL. > > > > I can send translated sgml to you. Do you want this? > > [ CC'ing docs list.] > > I am not sure how we handle translations of the docs. Folks? It sure is a really important question. A french team is in their way to do their own translation of the postgresql manual. It would be interesting if localized manuals could be integrated in the postgresql package. -- Guillaume . ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [DOCS] PostgreSQL Tutorial in Russian
On 30 Aug 2003 at 17:03, Guillaume LELARGE wrote: > Le Samedi 30 Août 2003 14:33, Bruce Momjian a écrit : > > I am not sure how we handle translations of the docs. Folks? > It sure is a really important question. A french team is in their way to do > their own translation of the postgresql manual. It would be interesting if > localized manuals could be integrated in the postgresql package. I know the FreeBSD team does translations for their documentation. Perhaps their methods could be used as a starting point. -- Dan Langille : http://www.langille.org/ ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [DOCS] [HACKERS] What goes into the security doc?
Dan Langille writes: > It has already been decided that we need something. Please point me to where this has been decided. -- Peter Eisentraut [EMAIL PROTECTED] ---(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] What goes into the security doc?
On 30 Aug 2003 at 17:37, Peter Eisentraut wrote: > Dan Langille writes: > > > It has already been decided that we need something. > > Please point me to where this has been decided. I'm sure you can google as well I can can. The original message in this thread referred to "PostgreSQL Password Cracker" posted on 2003- 01-02. You could also search for the subject of this message. When you find those you'll see that such a section was suggested. I took up the task, suggested some content. Then it lingered and was brought up again recently. Your objections are the first. I can't see why you, or anyone for that matter, can possibly object to a section titled security which points to the relevent components and parts within the documentation. As previously stated, what I have posted is a starting point. You aren't being asked to do the work. Why do you care if someone else does it? You may not need such documentation, but it will be useful to many. -- Dan Langille : http://www.langille.org/ ---(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] What goes into the security doc?
Dan Langille wrote: > On 30 Aug 2003 at 17:37, Peter Eisentraut wrote: > > > Dan Langille writes: > > > > > It has already been decided that we need something. > > > > Please point me to where this has been decided. > > I'm sure you can google as well I can can. The original message in > this thread referred to "PostgreSQL Password Cracker" posted on 2003- > 01-02. You could also search for the subject of this message. When > you find those you'll see that such a section was suggested. I took > up the task, suggested some content. Then it lingered and was > brought up again recently. Your objections are the first. > > I can't see why you, or anyone for that matter, can possibly object > to a section titled security which points to the relevent components > and parts within the documentation. As previously stated, what I have > posted is a starting point. > > You aren't being asked to do the work. Why do you care if someone > else does it? You may not need such documentation, but it will be > useful to many. I don't think we "decided" to add it, but no one has objected to the idea, except Peter recently. Does it make sense to have a security overview section in the documentation? -- 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 7: don't forget to increase your free space map settings
Re: [DOCS] [HACKERS] What goes into the security doc?
Bruce Momjian <[EMAIL PROTECTED]> writes: > I don't think we "decided" to add it, but no one has objected to the > idea, except Peter recently. Does it make sense to have a security > overview section in the documentation? I think it does. As I think Peter is trying to point out, you could almost get the same result just by having a fat index entry under "security", but I think people are more likely to notice a chapter or section in the Admin Guide with such a title. Also, once we have such a chapter, we might find it reads more naturally to move some of the existing discussions into it, leaving only a cross-reference where the material is now. regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend
