Ruby,
to my heat-challenged ears and eyes this message looks as if the python
server side scripting "python" is built for python 2.3; and your
installed python is 2.4
So... I recommend installing python 2.3 and try again.
Harald2005/6/23, Ruby Murillo <[EMAIL PROTECTED]>:
Hi,
The following bug has been logged online:
Bug reference: 1728
Logged by: Christian Mercure
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP
Description:unable to connect from other stations
Details:
I am evaluating backend server
On Fri, 24 Jun 2005, Christian Mercure wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1728
> Logged by: Christian Mercure
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: Windows XP
> Description:unable to connec
The following bug has been logged online:
Bug reference: 1730
Logged by: Krasimir dimitrov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Debian Linux
Description:insert into x1.tbl select x2.tbl dont work
Details:
Hello there,
I use pos
The following bug has been logged online:
Bug reference: 1731
Logged by: Adam Kruger
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.03
Operating system: Linux
Description:Indexes are corrupt following an unclean shutdown
Details:
I have encountered a condi
On Fri, Jun 24, 2005 at 04:08:58PM +0100, Krasimir dimitrov wrote:
>
> aiidatapro.net=# select * from cms.code_company;
> id_company_coded |uid_news_coded|
> fk_id_base_company_coded
> --+--+--
>
This problem shows up in the pglog for systems running
slony, but is not unique to slony necessarily.
The timestamp on queries logged to pglog corresponds
to the time the query was prepared rather than when
the query was run SPI_exec.
With slony, the same prepared statements may be used
for days
