[BUGS] general question and BUG #5038

[Sofer, Yuval]

Hi

how do I review list of bugs reported as  fixed for each Postgres version?

Is there any quick way to detect a fix of bug using Bug id?

I saw the "changes" section in each major release documentation (appendixes 
->release notes->changes), but should I read it all rather than search using 
some BUG ID ?

And specifically for  bug #5038 - was it fix in version 8.3.8 or in higher 
Postgres version?

Thanks

Yuval Sofer
BMC Software
CTM&D Business Unit
DBA Team
972-52-4286-282
yuval_so...@bmc.com

Re: [BUGS] wrong search_path being used

[Erika31]

Hi Tom,

Why not implement a session/database option to use (or not) the replanning
of such functions. This would allow existing PG clusters to behave as they
historically did, and would simultaneously allow users who want to have
benefit of dynamically changing "search_path" inside a function to obtain
the expected result.

IMO, the query plan cache is a huge mistake, if it couldn't be disabled (in
another way than using EXECUTE). Perhaps based on the volatility of the
function ?
I intensively use schemas in a "heavy" PG database (understand
business-oriented logic db) and I'm today blocked by not being able to
select schemas in functions called several times in a session, leading to
wrong results. If performance is a good thing, getting the expected result
is primordial.

Lastly, is it planned to resolve this bug quickly ?

Thanks for your attention - and your involvement in PG project ;-)




--
View this message in context: 
http://postgresql.1045698.n5.nabble.com/wrong-search-path-being-used-tp5739027p5752394.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #8079: pg_ctl is killed by windows service controller due to "Timed out waiting for server startup" event

[krzbia]

The following bug has been logged on the website:

Bug reference:  8079
Logged by:  Christopher Bialas
Email address:  krz...@interia.pl
PostgreSQL version: 9.2.4
Operating system:   Microsoft Windows 2008R2 Standard server
Description:

With very high load of the server during startup (e.g.  simultaneous logon
to local console) pg_ctl is being killed by windows service controller as it
does not respond on time. I've seen it with process explorer:
1. pg_ctl starts, then
2. postgres processing tasks start
3. pg_ctl is killed leaving postgres workers running.

As a result windows service is totally confused as service is dead, and it
cannot be started again as it finds out that postgres is already running.

The following is the excerpt from windows log:
http://schemas.microsoft.com/win/2004/08/events/event";>
- 
   
  0 
  4 
  0 
  0x80 
   
  227797 
  Application 
  mypc 
   
  
- 
  Waiting for server startup... 
  
  
  
 - http://schemas.microsoft.com/win/2004/08/events/event";>
  - 
 
0 
2 
0 
0x80 
 
227801 
Application 
mypc 
 

  - 
Timed out waiting for server startup 

  




-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #8080: 32-bit ODBC Driver Needs timestamp MetaData Type

[victor]

The following bug has been logged on the website:

Bug reference:  8080
Logged by:  Victor Reinhart
Email address:  vic...@maintstar.com
PostgreSQL version: 9.2.4
Operating system:   Windows XP
Description:

When using PowerBuilder to connect to Postgres using the latest 32-bit ODBC
Driver, there is no "timestamp" MetaData Type.  The closest type is
"timestamptz" which PowerBuilder doesn't understand, and can't be configured
to use.  The Progress Data Direct ODBC Driver has both "timestamp" and
"timestamp with timezone" types.  The "timestamp" type is usable in
PowerBuilder.  However, it must be purchased for each user.  It would be
very helpful if the ODBC Driver had the "timestamp" MetaData Type.




-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] general question and BUG #5038

[Jeff Davis]

On Wed, 2013-04-17 at 04:09 -0500, Sofer, Yuval wrote:
> how do I review list of bugs reported as  fixed for each Postgres
> version?
> 
>  
> 
> Is there any quick way to detect a fix of bug using Bug id? 

There is no actively-maintained bug database for postgres. The best way
is to search the archives and the commit logs to see if it's there.

I found this message:
http://www.postgresql.org/message-id/4aa8ca7b.4020...@enterprisedb.com

And this commit:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=4e2d5efc6a45b1f9f96df42629f6d1c7740e657e

> And specifically for  bug #5038 – was it fix in version 8.3.8 or in
> higher Postgres version? 

8.3.X is out of maintenance. I *strongly* encourage you to immediately
upgrade to 8.3.23, and then to come up with a plan to get on a supported
release soon (8.4 or later).

This particular fix is not in 8.3.8, but it is in 8.3.9.

Regards,
Jeff Davis 




-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs