Re: [BUGS] BUG #5800: "corrupted" error messages (encoding problem ?)

2011-04-26 Thread Dave Page
On Tue, Mar 22, 2011 at 7:07 AM, genamiga wrote: > I tried with 9.0.3...same problem... This should be resolved in 9.0.4 btw. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bu

Re: [BUGS] BUG #5800: "corrupted" error messages (encoding problem ?)

2011-04-26 Thread Carlo Curatolo
Just tested the 9.0.4...same problem I am affraid... -- View this message in context: http://postgresql.1045698.n5.nabble.com/BUG-5800-corrupted-error-messages-encoding-problem-tp3313951p4340437.html Sent from the PostgreSQL - bugs mailing list archive at Nabble.com. -- Sent via pgsql-bugs mail

Re: [BUGS] BUG #5800: "corrupted" error messages (encoding problem ?)

2011-04-26 Thread Dave Page
On Tue, Apr 26, 2011 at 10:07 AM, Carlo Curatolo wrote: > Just tested the 9.0.4...same problem I am affraid... Uh, that's odd. I've asked someone to see if we can reproduce it again. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com

Re: [BUGS] BUG #5297: Add XATMI C API

2011-04-26 Thread Michael Musgrove
We would certainly be very interested in testing XA support. Our project is called BlackTie - it's an XATMI implementation. We use the JBossTS transaction manager for the transaction engine - although JBossTS is written in Java, providing XA support was reasonably easy since it conforms to the

Re: [BUGS] BUG #5297: Add XATMI C API

2011-04-26 Thread Michael Musgrove
Sorry, the link I included was for committers. Try this instead https://anonsvn.jboss.org/repos/blacktie/trunk/atmibroker-xatmi/src/example/txfooapp/ and the project page is http://www.jboss.org/blacktie We would certainly be very interested in testing XA support. Our project is called BlackTi

Re: [BUGS] Setting timezone: is it bug or intended?

2011-04-26 Thread Bruce Momjian
Yura Sokolov wrote: > 21.03.2011 15:51, Susanne Ebrecht ?: > > Hello Yora Sokolov, > > > > Maybe this is not a bug - just an inconsistence: > > > > Look here (tested with 9.0): > > > > =# set timezone='+3.5'; > > SET > > =# select current_timestamp; > >now > > --

[BUGS] BUG #5994: Can't excute DBI->connect to oracle by client site

2011-04-26 Thread Li Hongbing
The following bug has been logged online: Bug reference: 5994 Logged by: Li Hongbing Email address: lihongb...@intasect.com.cn PostgreSQL version: PostgreSQL 8.4. Operating system: x86_64_unknonwn_linux_gnu Description:Can't excute DBI->connect to oracle by client sit

Re: [BUGS] Setting timezone: is it bug or intended?

2011-04-26 Thread Tom Lane
Bruce Momjian writes: > As far as how to even document this, I have no idea. It already is documented. See http://developer.postgresql.org/pgdocs/postgres/datatype-datetime.html#DATATYPE-TIMEZONES specifically the point that POSIX zone names have the opposite sign convention from ISO-8601. The

Re: [BUGS] Setting timezone: is it bug or intended?

2011-04-26 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian writes: > > As far as how to even document this, I have no idea. > > It already is documented. See > http://developer.postgresql.org/pgdocs/postgres/datatype-datetime.html#DATATYPE-TIMEZONES > specifically the point that POSIX zone names have the opposite sign > c

Re: [BUGS] Setting timezone: is it bug or intended?

2011-04-26 Thread Tom Lane
Bruce Momjian writes: > Tom Lane wrote: >> It already is documented. See >> http://developer.postgresql.org/pgdocs/postgres/datatype-datetime.html#DATATYPE-TIMEZONES >> specifically the point that POSIX zone names have the opposite sign >> convention from ISO-8601. >> >> The great thing about st