Re: [ADMIN] postgresql patching
Generally: Because the PostgreSQL coders/fixers/packagers are damn good about integrating needed fixes quickly, to obviate the need for spurious 'field patching' As an example: http://web.nvd.nist.gov/view/vuln/search-results?query=postgresqlsearch_type=allcves=on Note that the first handful of CVEs listed there are labeled 'pre-' 9.2.4, or 9.1.9. IE, these are remediated in most recent minor revisions of PostgreSQL code. If you're seeking to make other, 'off-trunk' mods to the code, experts here will chime in... Lou Picciano - Original Message - From: rajkphb To: pgsql-admin@postgresql.org Sent: Tue, 10 Sep 2013 03:17:04 - (UTC) Subject: [ADMIN] postgresql patching Hi, I am relatively new to postgresql. I did not find any detailed documentation on patching . Please provide me some links where i can get some note on postgresql patching. Why does postgres documentation does not have patching topic? Thanks Suhas View this message in context: postgresql patching Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
[ADMIN] postgresql patching
Hi, I am relatively new to postgresql. I did not find any detailed documentation on patching .Please provide me some links where i can get some note on postgresql patching.Why does postgres documentation does not have patching topic?Thanks Suhas -- View this message in context: http://postgresql.1045698.n5.nabble.com/postgresql-patching-tp5770236.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
Re: [ADMIN] postgresql patching
Check this out : http://www.postgresql.org/support/versioning/ Cheers, A.A. On Mon, Sep 9, 2013 at 8:17 PM, rajkphb rajkph...@gmail.com wrote: Hi, I am relatively new to postgresql. I did not find any detailed documentation on patching . Please provide me some links where i can get some note on postgresql patching. Why does postgres documentation does not have patching topic? Thanks Suhas -- View this message in context: postgresql patchinghttp://postgresql.1045698.n5.nabble.com/postgresql-patching-tp5770236.html Sent from the PostgreSQL - admin mailing list archivehttp://postgresql.1045698.n5.nabble.com/PostgreSQL-admin-f2076596.htmlat Nabble.com.
[ADMIN] upgrades and streaming replication
I just wanted to check if there are any updates on the preferred way to upgrade a group of servers that are using streaming replication with minimal downtime. Mailing list messages from a year or two ago pretty much state the following: * No current plans to come up with some new mechanism to automate this process, downtime is assumed. * If you want no downtime, use one of the userspace replication solutions. * Best option is to upgrade the master with pg_upgrade, then upgrade the slaves and re-copy your data. * While it's tempting to think you could just run pg_upgrade on all hosts to avoid the copy step, that will not work as something in the system catalog changes which will break replication. * No good options to speed up the slave copy - rsync will either use timestamps to figure out if a file changed (and streaming skews that), or checksumming (and checksumming is slow). Is that still pretty much the situation today with 9.2 and 9.3? Any good guides or BCPs for the standard procedure that emphasize limiting downtime and giving a good rollback path? Thanks, Charles -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
