lpython3.dll' inside
your lib directory (C:\Program Files\PostgreSQL\9.6\lib\plpython3.dll).
Please let us know if you have any more queries in this regards.
Vipul Shukla
EnterpriseDB Corporation
From: Alan Millington <admilling...@yahoo.co.uk>
To: EnterpriseDB Customer Support" &l
There were several queries in 2014 regarding the absence of plpython2.dll from
the Enterprise DB Postgres distribution for Win32. I should have thought that
this omission was simply an oversight, which would have been rectified by now.
However, I find that plpython2.dll is still missing from
There were several queries in 2014 regarding the absence of plpython2.dll from
the Enterprise DB Postgres distribution for Win32. I should have thought that
this omission was simply an oversight, which would have been rectified by now.
However, I find that plpython2.dll is still missing from
I am running Postgres 8.4.1 on Windows XP Professional Service Pack 3. My
database is UTF8. I use psql -f to load files containing DDL and DML commands.
I discovered a long time ago that psql does not like UTF8 files: it complains
about the byte order mark on the first line. Up to now I have
, and another
for Postgres.
From: Leif Biberg Kristensen l...@solumslekt.org
To: Postgres general mailing list pgsql-general@postgresql.org
Cc: Alan Millington admilling...@yahoo.co.uk
Sent: Thursday, 20 September 2012, 16:44
Subject: Re: [GENERAL] Using psql -f
for type bytea
To: Alan Millington admilling...@yahoo.co.uk
Cc: Postgres general mailing list pgsql-general@postgresql.org
Date: Wednesday, 31 August, 2011, 18:24
Alan Millington admilling...@yahoo.co.uk writes:
I recently hit an error when trying to insert into a bytea column. The
following
I am running Postgres 8.4.1 on Windows XP Professional Service Pack 3. My
database is UTF8. My program code is written in Python, and to interface to
Postgres I use mxODBC 3.0 and the PostgreSQL Unicode driver PSQLODBCW.DLL
version 8.01.02.00 dated 31/01/2006.
I recently hit an error when
Lane t...@sss.pgh.pa.us
Subject: Re: [GENERAL] When is an explicit cast necessary?
To: Martijn van Oosterhout klep...@svana.org
Cc: Alan Millington admilling...@yahoo.co.uk, Alban Hertroys
dal...@solfertje.student.utwente.nl, Greg Smith g...@2ndquadrant.com,
Postgres general mailing list pgsql
twice. I do not regard that as an improvement!
--- On Sat, 10/4/10, Alban Hertroys dal...@solfertje.student.utwente.nl wrote:
From: Alban Hertroys dal...@solfertje.student.utwente.nl
Subject: Re: [GENERAL] When is an explicit cast necessary?
To: Alan Millington admilling...@yahoo.co.uk
Cc: Greg
I am using Postgres 8.4.1 on Windows XP Professional Service Pack 3.
I have a PL/pgSQL function which is defined as returns record. The record
contains three values. In one execution path, the values are read from a table,
the selected columns being of types int, smallint and char(1). In
Millington admilling...@yahoo.co.uk
Cc: Postgres general mailing list pgsql-general@postgresql.org
Date: Friday, 9 April, 2010, 15:06
Alan Millington wrote:
As far as I remember, when I was using Postgres 8.1.4 that worked, but under
Postgres 8.4.1 it results in the errors Returned type integer
You probably need to ask the mxODBC developers (who AFAIK don't hang out
on this list) what they are doing with that data. It sounds fairly
likely to me that the bytea value is just being sent as a string without
any special encoding. That would explain both the null sensitivity you
mention
Today for the first time since upgrading to Postgres 8.4.1 I tried
out part of the code which inserts some binary data into a table. The
insert failed with the error invalid byte sequence for encoding
UTF8. That is odd, because the column into which the insert was made
is of type bytea: the
Having done some investigation, I can shed further light on the problem.
Within an interactive Python session I connected to the database using mxODBC:
the variable csr is an mxODBC cursor object. I made the following assignments:
sql = 'insert into mytable (seq_num, data) values (?, ?)'
data
I am running Postgres 8.4.1 on Windows XP Professional Service Pack 3. My
database is UTF8. My program code is written in Python, and to interface to
Postgres I use mxODBC 3.0 and the PostgreSQL Unicode driver PSQLODBCW.DLL
version 8.01.02.00 dated 31/01/2006.
Today for the first time since
On 19/08/2009 6:38 PM, Craig Ringer wrote:
Got a virus scanner installed? If so, remove it (do not just disable it) and
see if you can reproduce the problem. Ditto anti-spyware software.
You should also `chkdsk' your file system(s) and use a SMART diagnostic tool to
test your hard disk
I am running Postgres 8.1.4 on Windows XP Professional Service Pack 3.
Yesterday when attempting to select from one particular database I repeatedly
encountered errors such as the following:
2009-08-18 10:49:54 ERROR: could not open relation 1663/51796/1247: No such
file or directory
I note that plpython.dll references a specific Python version. In the case of
Postgres 8.1.4, which is what I have installed, the reference is to
Python24.dll.
Is there yet a Postgres version in which plpython.dll references Python26.dll?
(I am running on Windows XP Professional Service Pack
I am running Postgres 8.1.4 on Windows XP Professional Service Pack 3.
I recently tried to make a copy of an existing database. I made a dump using
pg_dump -Fc, I created a new database from template0, and attempted to restore
into it using pg_restore. The tables were created and about half
your advice, and use EXTRACT instead, if that is going to be more
robust.
--- On Mon, 13/7/09, Tom Lane t...@sss.pgh.pa.us wrote:
From: Tom Lane t...@sss.pgh.pa.us
Subject: Re: [GENERAL] Problem with Check Constraint in pg_restore
To: Alan Millington admilling...@yahoo.co.uk
Cc: pgsql-general
20 matches
Mail list logo
