Store using Postgres 9 with Windows 7

Greetings,

I am running VisualWorks® NonCommercial, 7.6 and Postgres 9 x.64 on Windows 7.

I can connect to the Store repository (on my machine) but when I attempt to "Compare With.." a version from the repository I get:

ERROR:  Message not understood: #bitShift:

I can connect to the Cincom repository and perform a "Compare With..." with no problem so I conclude that this may be a problem with the version of Postgresql I am using.

Has anyone has similar problem and if yes, how did you solve it.

Thanks,
Frank

Frank,

You need to change the below line in your postgresql.conf as follows and restart the service,

bytea_output = 'escape' # hex, escape

Also, see recent discussion (attached) as to how this could be transparently addressed in the EXDI driver.

-Boris

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Flynch55
Sent: Sunday, August 07, 2011 4:08 PM
To: [hidden email]
Subject: [vwnc] Store using Postgres 9 with Windows 7

Greetings,

I am running VisualWorks® NonCommercial, 7.6 and Postgres 9 x.64 on Windows 7.

I can connect to the Store repository (on my machine) but when I attempt to "Compare With.." a version from the repository I get:

ERROR:  Message not understood: #bitShift:

I can connect to the Cincom repository and perform a "Compare With..." with no problem so I conclude that this may be a problem with the version of Postgresql I am using.

Has anyone has similar problem and if yes, how did you solve it.

Thanks,
Frank

--
View this message in context: http://forum.world.st/Store-using-Postgres-9-with-Windows-7-tp3725534p3725534.html
Sent from the VisualWorks mailing list archive at Nabble.com.

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Ah, ok. That makes sense.



  _____  


Boris <mailto:[hidden email]>  Popov, DeepCove Labs
June 17, 2011 10:56 AM



Alan,

 

I think what Henrik is suggesting is to modify the driver to recognize the encoding from the result set (by looking for \x at the beginning and using existing bytea when absent). The server recognizes both formats for the input, so you could stick with bytea for backwards-compatibility,

 

http://www.postgresql.org/docs/9.0/static/datatype-binary.html

 

-Boris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Alan Knight
Sent: 17 June 2011 10:40
To: Henrik Sperre Johansen
Cc: VWDEV List
Subject: Re: Fwd: Re: bytea columns in Postgres driver

 

The problem, of course, with that sort of change is that with many repositories they may be accessed by a wide range of clients, from different versions. So needing to modify or update your driver would be unpleasant as, say, a requirement for accessing the public repository.



Henrik Sperre <mailto:[hidden email]>  Johansen
June 17, 2011 9:33 AM

 


Struck again by the default reply recipient...

-------- Original Message --------


Subject:

Re: bytea columns in Postgres driver


Date:

Fri, 17 Jun 2011 15:04:35 +0200


From:

Henrik Sperre Johansen  <mailto:[hidden email]> <[hidden email]>


To:

Boris Popov, DeepCove Labs  <mailto:[hidden email]> <[hidden email]>

 

On 17.06.2011 14:36, Boris Popov, DeepCove Labs wrote:
> Henrik, there's an option in postgresql.conf to go back to bytea convention in 9.0+ for the time being.
>
> Sent from my iPhone
>
> On 2011-06-17, at 6:03, "Henrik Sperre Johansen" <mailto:[hidden email]> <[hidden email]> wrote:
>
Hehe, for the time being, I hacked the driver instead and added an extra
conversion step on the way back if a hex-formatted string was returned, seemed faster than
reading more documentation :)

The issue of a non-standard way being used to store bytearrays still
remain though.

Cheers,
Henry

  _____  


Alan Knight <mailto:[hidden email]>
June 17, 2011 10:40 AM


The problem, of course, with that sort of change is that with many repositories they may be accessed by a wide range of clients, from different versions. So needing to modify or update your driver would be unpleasant as, say, a requirement for accessing the public repository.

  _____  


Henrik Sperre Johansen <mailto:[hidden email]>
June 17, 2011 9:33 AM


Struck again by the default reply recipient...

-------- Original Message --------
Subject: Re: bytea columns in Postgres driver
Date: Fri, 17 Jun 2011 15:04:35 +0200
From: Henrik Sperre Johansen  <mailto:[hidden email]> <[hidden email]>
To: Boris Popov, DeepCove Labs  <mailto:[hidden email]> <[hidden email]>


On 17.06.2011 14:36, Boris Popov, DeepCove Labs wrote:
> Henrik, there's an option in postgresql.conf to go back to bytea convention in 9.0+ for the time being.
>
> Sent from my iPhone
>
> On 2011-06-17, at 6:03, "Henrik Sperre Johansen" <mailto:[hidden email]> <[hidden email]> wrote:
>
Hehe, for the time being, I hacked the driver instead and added an extra
conversion step on the way back if a hex-formatted string was returned, seemed faster than
reading more documentation :)

The issue of a non-standard way being used to store bytearrays still
remain though.

Cheers,
Henry



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

more ..

I replaced Postgresql 9 with Postgresql 8.4.8.1 and everything works perfectly.

I am guessing that there is some problem using Postgresql 9.0 on a Windows 7 box.

Cheers,
Frank

Have a look at my recent response. It's a configuration option you need to change in pgsql until VW is patched to be compatible with both new and old style out of the box.

Sent from my iPhone

On 2011-08-07, at 16:36, "Flynch55" <[hidden email]> wrote:

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc