Re: [DOCS] Updated Russian translation of FAQ
Patch applied. Thanks. --- Viktor Vislobokov wrote: > Hello. > > There is updated Russian translation of FAQ in attachment. > > -- > With best wishes, > Victor Vislobokov > Perm. Russia > > [ application/x-gzip is not supported, skipping... ] -- 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 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[DOCS] Added documentation about caching, reliability
I have added a section to the top of the WAL docs explaining caching and reliability issues: http://candle.pha.pa.us/main/writings/pgsql/sgml/reliability.html I also renamed the chapter "Reilability" rather than "WAL." -- 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 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [DOCS] [HACKERS] Added documentation about caching, reliability
Thanks, fixed. --- Jonah H. Harris wrote: > Hey Bruce, > > One grammar issue... otherwise great work. > > they can be moved to another computer with similar hardware and all > committed transaction will remain intact. > > should be > > they can be moved to another computer with similar hardware and all > committed transactions will remain intact. > > On 9/28/05, Bruce Momjian wrote: > > > > I have added a section to the top of the WAL docs explaining caching and > > reliability issues: > > > > http://candle.pha.pa.us/main/writings/pgsql/sgml/reliability.html > > > > I also renamed the chapter "Reilability" rather than "WAL." > > > > -- > > 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 1: 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 > > > > > > -- > Respectfully, > > Jonah H. Harris, Database Internals Architect > EnterpriseDB Corporation > http://www.enterprisedb.com/ -- 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: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [DOCS] Added documentation about caching, reliability
On Wed, Sep 28, 2005 at 02:26:24PM -0400, Bruce Momjian wrote: > I have added a section to the top of the WAL docs explaining caching and > reliability issues: > > http://candle.pha.pa.us/main/writings/pgsql/sgml/reliability.html > > I also renamed the chapter "Reilability" rather than "WAL." While you are re-titling the docs, maybe the sections on that chapter could be titled "Benefits of Write-Ahead Log" instead of "Benefits of WAL", etc. -- Alvaro Herrera http://www.amazon.com/gp/registry/DXLWNGRJD34 "La realidad se compone de muchos sueños, todos ellos diferentes, pero en cierto aspecto, parecidos..." (Yo, hablando de sueños eróticos) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[DOCS] INSTALL file nits
I just grabbed a copy of PostgreSQL from http://www.apple.com/downloads/macosx/unix_open_source/postgresql.html and installed it on my Mac OS X (Tiger; 10.4.2) machine. I followed the "Short Version" in the INSTALL file until I ran into problems, then did some workarounds, as discussed below. Perhaps this file should be made a bit more explicit or an INSTALL.OSX file could be generated... ./configure No reported problems. gmake No such command, but I ran "make --version" and saw that it was GNU Make, so I used it. No reported problems. su This command requires a root password, which does not exist. OSX uses "sudo -s" for this sort of thing. gmake install Used make; no reported problems. adduser postgres No such command. I considered using System Preferences > Accounts to add a user, but this seemed like a rather bogus approach, as it would put a user in the Login dialog (unlike lp, postfix, ...). I found a (slightly dated) note from Apple, however, that suggested just this approach, so I gave it a try. http://developer.apple.com/internet/opensource/postgres.html mkdir /usr/local/pgsql/data chown postgres /usr/local/pgsql/data No reported problems. su - postgres No reported problems (when run under sudo). /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data >logfile 2>&1 & /usr/local/pgsql/bin/createdb test /usr/local/pgsql/bin/psql test No reported problems, but the last command left me at a prompt with no particular instructions as to what I should do next. -r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com- Canta Forda Computer Laboratory http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. ---(end of broadcast)--- TIP 1: 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] INSTALL file nits
Hello! Not clear if you're new to PostgreSQL or not, but regardless, a warm welcome is extended. On Sep 29, 2005, at 10:29 , Rich Morin wrote: I just grabbed a copy of PostgreSQL from http://www.apple.com/downloads/macosx/unix_open_source/ postgresql.html Nifty! I didn't know Apple had a link there. And it's even a recent version! and installed it on my Mac OS X (Tiger; 10.4.2) machine. I followed the "Short Version" in the INSTALL file until I ran into problems, then did some workarounds, as discussed below. The short version is definitely that: short. It ceases to be short when one adds all of the caveats for all of the various systems and environments in which PostgreSQL will run. Perhaps this file should be made a bit more explicit or an INSTALL.OSX file could be generated... One of the joys of open source is that the community can contribute, be that source code or documentation. (hint hint) adduser postgres No such command. I considered using System Preferences > Accounts to add a user, but this seemed like a rather bogus approach, as it would put a user in the Login dialog (unlike lp, postfix, ...). I found a (slightly dated) note from Apple, however, that suggested just this approach, so I gave it a try. To get around this, you can create a user using NetInfo (or nicl or niutil at the command line) by copying another user, such as www. Make sure the userid is low (less than 100, iirc) and they will not appear in the login window, nor will a home folder be created. I use this technique for setting up a svn user on my machine (though I haven't done it yet for a postgres user). Depending on your needs, you may want to bump up the shmmall and shmmax values in /etc/rc. They're quite small on a default Mac OS X install. I've needed to increase them if I'm running more than one installation of PostgreSQL on my box, or if I'm increasing the number of allowed connections to the server. With 2GB of available RAM, I allocated 256MB rather than the default 4MB. (I include the notes in the /etc/rc file so I remember what it was I did.) Here are my settings # original supplied with Mac OS X 10.4 # sysctl -w kern.sysv.shmmax=4194304 kern.sysv.shmmin=1 kern.sysv.shmmni=32 kern.sysv.shmseg=8 kern.sysv.shmall=1024 # Defaults are for 4MB # shmmax (4MB * 1024KB/MB * 1024 bytes/KB = 4194304 bytes) # shmall (4MB @ 4K/page => 1024 pages) # Increase to 256MB # shmmax (256MB * 1024KB/MB * 1024 bytes/KB = 268435456) # shmall (256MB @ 4K/page => 65536 pages) sysctl -w kern.sysv.shmmax=268435456 kern.sysv.shmmin=1 kern.sysv.shmmni=32 kern.sysv.shmseg=8 kern.sysv.shmall=65536 Don't know if this will be necessary for you, but thought you might like to know. Michael Glaesemann grzm myrealbox com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [DOCS] Added documentation about caching, reliability
Alvaro Herrera wrote: > On Wed, Sep 28, 2005 at 02:26:24PM -0400, Bruce Momjian wrote: > > I have added a section to the top of the WAL docs explaining caching and > > reliability issues: > > > > http://candle.pha.pa.us/main/writings/pgsql/sgml/reliability.html > > > > I also renamed the chapter "Reilability" rather than "WAL." > > While you are re-titling the docs, maybe the sections on that chapter > could be titled "Benefits of Write-Ahead Log" instead of "Benefits of > WAL", etc. The chapter sections are: Table of Contents 26.1. Write-Ahead Logging (WAL) 26.2. Benefits of WAL 26.3. WAL Configuration 26.4. WAL Internals Are you suggesting we spell out Write-Ahead Logging for all section titles? -- 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 6: explain analyze is your friend
Re: [DOCS] INSTALL file nits
At 10:59 AM +0900 9/29/05, Michael Glaesemann wrote: Not clear if you're new to PostgreSQL or not, but regardless, a warm welcome is extended. Thanks! I've been lurking on this list for quite a while. I published the PostgreSQL manuals a few years ago (under the PTF/Dossier imprint), but that enterprise wasn't profitable enough to sustain itself. I also hang out with some PostgreSQL types in the SF Bay Area and have been looking at using PostgreSQL with Ruby on Rails, because it handles some things that neither MySQL nor Rails does (in any reasonable fashion :-). The short version is definitely that: short. It ceases to be short when one adds all of the caveats for all of the various systems and environments in which PostgreSQL will run. Yeah, well, I _did_ scan down the file in search of specific OSXisms. One of the joys of open source is that the community can contribute, be that source code or documentation. (hint hint) Well, I'm not really expert enough to document the "right" Way To Do It, but reporting bugs isn't chopped liver... adduser postgres No such command. I considered using System Preferences > Accounts to add a user, but this seemed like a rather bogus approach, as it would put a user in the Login dialog (unlike lp, postfix, ...). I found a (slightly dated) note from Apple, however, that suggested just this approach, so I gave it a try. To get around this, ... See, you have all this wonderful arcana at your fingertips. Why not put it in an OSX-specific README, let it bounce across the list a few times, and put it in the distro (or on a wiki, if that's preferable)? Thanks, in any case, for the useful hints... -r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com- Canta Forda Computer Laboratory http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [DOCS] Added documentation about caching, reliability
On Wed, Sep 28, 2005 at 10:08:02PM -0400, Bruce Momjian wrote: > The chapter sections are: > > Table of Contents > 26.1. Write-Ahead Logging (WAL) > 26.2. Benefits of WAL > 26.3. WAL Configuration > 26.4. WAL Internals > > Are you suggesting we spell out Write-Ahead Logging for all section > titles? Is it considered good style to use acronyms in titles? I wouldn't do it. Maybe it could be left as 26.1. Write-Ahead Logging 26.2. Benefits of Write-Ahead Logging 26.3. WAL Configuration 26.4. WAL Internals because the former two talk about WAL in a general manner, while the latter two are about our implementation. I also wouldn't expand the acronym in a title. -- Alvaro Herrera Valdivia, Chile ICBM: S 39º 49' 17.7", W 73º 14' 26.8" Thou shalt study thy libraries and strive not to reinvent them without cause, that thy code may be short and readable and thy days pleasant and productive. (7th Commandment for C Programmers) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [DOCS] Added documentation about caching, reliability
Alvaro Herrera wrote: > On Wed, Sep 28, 2005 at 10:08:02PM -0400, Bruce Momjian wrote: > > > The chapter sections are: > > > > Table of Contents > > 26.1. Write-Ahead Logging (WAL) > > 26.2. Benefits of WAL > > 26.3. WAL Configuration > > 26.4. WAL Internals > > > > Are you suggesting we spell out Write-Ahead Logging for all section > > titles? > > Is it considered good style to use acronyms in titles? I wouldn't do it. > > Maybe it could be left as > > 26.1. Write-Ahead Logging > 26.2. Benefits of Write-Ahead Logging I modified 26.2 as you suggested. > 26.3. WAL Configuration > 26.4. WAL Internals > > because the former two talk about WAL in a general manner, while the > latter two are about our implementation. I also wouldn't expand the > acronym in a title. I think we do need to show the acronym in the title if use that acronym in later titles. -- 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 1: 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] Added documentation about caching, reliability
Am Mittwoch, 28. September 2005 20:26 schrieb Bruce Momjian: > I also renamed the chapter "Reilability" rather than "WAL." Considering that the chapter is, in fact, all about WAL, I don't think this is a good move. Reliability is a concern that is not only addressed by the WAL system. Please change it back. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
