all we know at this point, the error is with your XA manager, not with
Postgres.
If you want to be sure, grep the source of the JDBC driver for those error
codes; I doubt you'll find them in there.
Google was kind enough to point me here:
http://jdbc.postgresql.org/development/git.html
On 5 February 2013 17:06, Amit Kapila wrote:
> Tuesday, February 05, 2013 12:40 PM nvardar wrote:
> > throws;
> >
> > >[Error] Script lines: 1-20 -
> > ERROR: Node 2 has aborted execution, cause is:
> > com.edb.gridsql.exception.XDBServerException :
> > java.lang.NullPoin
On 19 July 2012 13:50, Alexander Law wrote:
>> I like Craig's idea of adding the client encoding to the log lines. A
>> possible problem with that (I'm not an encoding expert) is that a log
>> line like that will contain data about the database server meta-data
>> (log time, client encoding, etc)
Yikes, messed up my grammar a bit I see!
On 19 July 2012 10:58, Alban Hertroys wrote:
> I like Craig's idea of adding the client encoding to the log lines. A
> possible problem with that (I'm not an encoding expert) is that a log
> line like that will contain data about the d
On 19 July 2012 10:40, Alexander Law wrote:
>>> Ok, maybe the time of real universal encoding has not yet come. Then
>>> we maybe just should add a new parameter "log_encoding" (UTF-8 by
>>> default) to postgresql.conf. And to use this encoding consistently
>>> within logging_collector.
>>> If thi
