Re: [ADMIN] Postgresql Upgrade 7.4 to 8.2
On 01/25/07 06:11, Joshua D. Drake wrote: Peter Eisentraut wrote: Radhika Sambamurti wrote: 1. How is the backup and recovery using WAL logging in 8.2 It's great! Less filling! Seriously though, the PITR recovery mechanism is quite mature and usable. I would say it is a good start - and progress is clearly being made. But it wont be usable for most serious applications until we have per-database transaction logging and backup recovery. Having to run a new instance (or obliterate the main instance) for recovery simply isn't practical. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [ADMIN] Postgresql Upgrade 7.4 to 8.2
Zach Bagnall [EMAIL PROTECTED] writes: Seriously though, the PITR recovery mechanism is quite mature and usable. I would say it is a good start - and progress is clearly being made. But it wont be usable for most serious applications until we have per-database transaction logging and backup recovery. Don't hold your breath; that's not even on the agenda, much less something that's likely to appear soon. If you need separable recovery then run a different postmaster instance for each database. regards, tom lane ---(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: [ADMIN] Postgresql Upgrade 7.4 to 8.2
Tom Lane wrote: Zach Bagnall [EMAIL PROTECTED] writes: Seriously though, the PITR recovery mechanism is quite mature and usable. I would say it is a good start - and progress is clearly being made. But it wont be usable for most serious applications until we have per-database transaction logging and backup recovery. Don't hold your breath; that's not even on the agenda, much less something that's likely to appear soon. If you need separable recovery then run a different postmaster instance for each database. I would have to concur... if you need such a feature I would wonder why you are running multiple databases within the same cluster at all. Joshua D. Drake regards, tom lane -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [ADMIN] Postgresql Upgrade 7.4 to 8.2
On 02/14/07 16:00, Joshua D. Drake wrote: Tom Lane wrote: Zach Bagnall [EMAIL PROTECTED] writes: Seriously though, the PITR recovery mechanism is quite mature and usable. I would say it is a good start - and progress is clearly being made. But it wont be usable for most serious applications until we have per-database transaction logging and backup recovery. Don't hold your breath; that's not even on the agenda, much less something that's likely to appear soon. If you need separable recovery then run a different postmaster instance for each database. I would have to concur... if you need such a feature I would wonder why you are running multiple databases within the same cluster at all. It's not exactly an exotic feature. Sybase has had it for as long as I can remember, as has Informix and DB2 (I'm told). The obvious reason for not running multiple instances is that postgresql will know how to use the available memory most efficiently. By splitting them up, each postmaster must be tuned and adjusted by a stupid human. Unless you meant using a new hardware server for each database.. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[ADMIN] Postgresql Upgrade 7.4 to 8.2
Hi, I am soon going to be testing postgresql upgrades from our ancient 7.4 version to the latest 8.2. Part of the reason (apart from the obvious) is that I want to implement WAL logging for backup and recovery. Some general questions I have are: 1. How is the backup and recovery using WAL logging in 8.2 Currently we use Slony for replication, but have no PITR / backup in place, which makes me very nervous. Any insights on upgrading will also help. Thank you, Radhika -- It is all a matter of perspective. You choose your view by choosing where to stand. Larry Wall --- ---(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: [ADMIN] Postgresql Upgrade 7.4 to 8.2
Any insights on upgrading will also help. Thank you, Radhika Hello! About upgrading you should read these links: http://www.postgresql.org/docs/8.2/interactive/install-upgrading.html and http://www.postgresql.org/docs/8.2/interactive/migration.html Greetings, Matthias ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] Postgresql Upgrade 7.4 to 8.2
Radhika Sambamurti написа: [...] Some general questions I have are: 1. How is the backup and recovery using WAL logging in 8.2 Currently we use Slony for replication, but have no PITR / backup in place, which makes me very nervous. [...] Also these: http://www.postgresql.org/docs/8.2/static/continuous-archiving.html http://www.postgresql.org/docs/8.2/static/warm-standby.html -- Milen A. Radev ---(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: [ADMIN] Postgresql Upgrade 7.4 to 8.2
Radhika Sambamurti wrote: 1. How is the backup and recovery using WAL logging in 8.2 It's great! -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [ADMIN] Postgresql Upgrade 7.4 to 8.2
Peter Eisentraut wrote: Radhika Sambamurti wrote: 1. How is the backup and recovery using WAL logging in 8.2 It's great! Less filling! Seriously though, the PITR recovery mechanism is quite mature and usable. Sincerely, Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
