Re: [DOCS] Postgres Sql7.3 Update
On Wed, Sep 2, 2009 at 1:09 PM, kunwarpal.rawat wrote: > Dear Support Team, > > > > I am currently using postgresql version 7.3 and I want to upgrade this > version. > > So, can you please help me regarding the > > 1. List of upgrades/patches/service packs available to update the > postgresql 7.3 version There were 21 patch releases available for 7.3. You can see the list on this page and see what bugs and security holes they fixed: http://www.postgresql.org/docs/8.4/static/appendixes.html However you should realize that 7.3.21 came out a year and a half ago and was the end of life for 7.3. If any further bugs or security holes have been found they would not generally be fixed. Users are advised to upgrade to a supported release. > 2. The list of feature that’s updating in each new version of the > software. That same link has the release notes for versions 7.4, 8.0, 8.1, 8.2, 8.3, and 8.4 along with all the patch releases for them. It will take a long time to read as you're talking about 6 years of development. -- greg http://mit.edu/~gsstark/resume.pdf -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Postgres Sql7.3 Update
On Thu, Sep 03, 2009 at 12:03:35PM +0100, Greg Stark wrote: > On Wed, Sep 2, 2009 at 1:09 PM, > kunwarpal.rawat wrote: > > Dear Support Team, > > > > > > > > I am currently using postgresql version 7.3 and I want to upgrade this > > version. > > > > So, can you please help me regarding the > > > > 1. List of upgrades/patches/service packs available to update the > > postgresql 7.3 version > > There were 21 patch releases available for 7.3. You can see the list > on this page and see what bugs and security holes they fixed: > > http://www.postgresql.org/docs/8.4/static/appendixes.html > > However you should realize that 7.3.21 came out a year and a half ago > and was the end of life for 7.3. If any further bugs or security holes > have been found they would not generally be fixed. With all due respect, you should not have put any qualifiers in that sentence. 7.3 is as dead a King Charles, and if someone finds a remote root exploit in it, it will not be fixed. > Users are advised to upgrade to a supported release. In the sense that people sailing in small boats on rough water are "advised" to wear a life vest, yes. > > 2. The list of feature that’s updating in each new version > > of the software. > > That same link has the release notes for versions 7.4, 8.0, 8.1, > 8.2, 8.3, and 8.4 along with all the patch releases for them. It > will take a long time to read as you're talking about 6 years of > development. It's a really, really good idea to build major version upgrades into your development, deployment and maintenance processes. Cheers, David. -- David Fetter http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: [email protected] Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Postgres Sql7.3 Update
On Wed, Sep 2, 2009 at 6:09 AM, kunwarpal.rawat wrote: > Dear Support Team, > > I am currently using postgresql version 7.3 and I want to upgrade this > version. I'm gonna assume you mean upgrade off of 7.3 to a newer version. That would be a good idea. 7.3 is really old, unsupported and pretty slow compared to newer versions. > So, can you please help me regarding the > > 1. List of upgrades/patches/service packs available to update the > postgresql 7.3 version PostgreSQL isn't generally "patched" like Oracle, but has new releases generally available through packages. There's also the one click installers and building from source. So, what OS are you running, and how was pgsql installed? > 2. The list of feature that’s updating in each new version of the > software. For an upgrade from 7.3 to 8.4??? Way too many to list in one post. For an update like 7.3.1 to 7.3.21, there aren't any feature enhancements really, since feature enhancements are generally limited to new releases (i.e. 8.0.x to 8.1.x). Basically, the biggest feature enhancements from each major release since 7.3 has been more performance, and overall improvement of the dbms in terms of things like vacuuming and recovery and more. -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Postgres Sql7.3 Update
On Wed, Sep 2, 2009 at 7:09 AM, kunwarpal.rawat wrote: > > 2. The list of feature that’s updating in each new version of the > software. > http://www.postgresql.org/about/featurematrix -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Postgres Sql7.3 Update
[email protected] ("kunwarpal.rawat") writes: > > I am currently using postgresql version 7.3 and I want to upgrade this > version. > > So, can you please help me regarding the > > 1. List of upgrades/patches/service packs available to update the > postgresql 7.3 version It's no longer a supported version, so you'll not find very much that's specific to 7.3. Since 7.3.21, released over a year ago, was the last update, it is highly likely that you will want to upgrade to something rather less dramatically out of date than 7.3. Upgrading to 8.4 (the latest stable release) would involve, at least in general terms: - Dumping the 7.3 database using pg_dump from 8.4 (It's possible that the 8.4 pg_dump is "too new" and doesn't still remember all the details of any oddities of 7.3; you'll want to test this, and might discover you need to go thru some interim version to get to what you finally want to be on) - Loading that into the new DB There may be changes needed to such things as: - data types (though I don't think there'll be *too* much - a lot of the scary such changes were between 6.5 and 7.0) - queries may need to be revised, as recent versions are sometimes stricter about what kinds of data may be joined/compared > 2. The list of feature that?s updating in each new version of the > software. See: http://www.postgresql.org/docs/8.4/static/release.html which points you to: http://www.postgresql.org/docs/8.4/static/release-8-4.html http://www.postgresql.org/docs/8.4/static/release-8-3.html http://www.postgresql.org/docs/8.4/static/release-8-2.html http://www.postgresql.org/docs/8.4/static/release-8-1.html http://www.postgresql.org/docs/8.4/static/release-8-0.html http://www.postgresql.org/docs/8.4/static/release-7-4.html http://www.postgresql.org/docs/8.4/static/release-7-3.html There's a lot of reading to do! -- let name="cbbrowne" and tld="ca.afilias.info" in name ^ "@" ^ tld;; Christopher Browne "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three" -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] [GENERAL] What happens when syslog gets blocked?
decibel wrote: > On Aug 6, 2009, at 2:00 PM, Bill Moran wrote: > >Well ... "life better" really depends on which failure scenario you're > >more comfortable with ... personally, I'd rather lose log messages > >than > >have the DB system go down. Of course, if auditing is critical to > >your > >scenario, then your priorities are different ... > > Bingo. I'm thinking we should make mention of this in the docs... I propose the following patch. -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. Index: doc/src/sgml/config.sgml === RCS file: /home/alvherre/Code/cvs/pgsql/doc/src/sgml/config.sgml,v retrieving revision 1.224 diff -c -p -r1.224 config.sgml *** doc/src/sgml/config.sgml 24 Aug 2009 20:08:31 - 1.224 --- doc/src/sgml/config.sgml 3 Sep 2009 22:03:00 - *** local0.*/var/log/postgresql *** 2408,2413 --- 2408,2426 is dynamic-linker failure messages). This parameter can only be set at server start. + + + + The logging collector is designed to never lose messages. This means + that in case of extremely high load, server processes could be + blocked due to trying to send additional log messages when the + collector has fallen behind. In contrast, syslog + prefers to drop messages if it cannot write them, which means it's + less reliable in those cases but it will not block the rest of the + system. + + + -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
