Skip site navigation (1) Skip section navigation (2)

Re: Known Issues Page

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: "Tharakan, George (GE Healthcare)" <George(dot)Tharakan(at)ge(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Known Issues Page
Date: 2010-03-29 11:16:11
Message-ID: 4BB08BFB.6040207@kaltenbrunner.cc (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Tharakan, George (GE Healthcare) wrote:
> Hi,
>  
> I have been using PostGreSQL as a part of our healthcare product. As 
> an important part of releasing a stable product it is important to also 
> document the known issues found in a PostGRE release. I would be 
> grateful if someone could forward me to the Known Issues Page(if any). 
> On these lines http://www.postgresql.org/support/security.html has been 
> very helpful but it only caters to security.

this is not a bug so the wrong place to ask but anyway...
If you are looking for what exactly was changed in a given minor release 
just look at the release notes:

http://www.postgresql.org/docs/current/static/release.html

so if you for example want to upgrade from 8.4.1 to 8.4.3 you would 
simply read the release notes for 8.4.2 and 8.4.3.


Stefan

In response to

pgsql-hackers by date

Next:From: Ɓukasz DejnekaDate: 2010-03-29 11:18:04
Subject: Using HStore type in TSearch
Previous:From: Gokulakannan SomasundaramDate: 2010-03-29 10:42:08
Subject: Re: GSoC Query

pgsql-bugs by date

Next:From: Peter EisentrautDate: 2010-03-29 21:36:42
Subject: Re: BUG #5272: PL/Python SELECT: return composite fields as dict, not str
Previous:From: Takahiro ItagakiDate: 2010-03-29 09:47:05
Subject: Re: BUG #5394: invalid declspec for PG_MODULE_MAGIC

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group