Re: [GENERAL] plpython2.dll missing from Enterprise DB Postgres distribution

2017-09-06 Thread Alan Millington
ry (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 To: EnterpriseDB Customer Support" Sent: 25 Aug 2017, 12:12 PM My question was concerning plpython2.dll, not plp

[GENERAL] plpython2.dll missing from Enterprise DB Postgres distribution

2017-08-24 Thread Alan Millington
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 the

[GENERAL] plpython2.dll missing from Enterprise DB Postgres distribution

2017-08-24 Thread Alan Millington
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 the

Re: [GENERAL] Using psql -f to load a UTF8 file

2012-09-20 Thread Alan Millington
itor for Python, and another for Postgres.   From: Leif Biberg Kristensen To: Postgres general mailing list Cc: Alan Millington Sent: Thursday, 20 September 2012, 16:44 Subject: Re: [GENERAL] Using psql -f to load a UTF8 file Torsdag 20. september 2012

[GENERAL] Using psql -f to load a UTF8 file

2012-09-20 Thread Alan Millington
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 wor

Re: [GENERAL] "invalid input syntax for type bytea"

2011-09-01 Thread Alan Millington
ytea" To: "Alan Millington" Cc: "Postgres general mailing list" Date: Wednesday, 31 August, 2011, 18:24 Alan Millington writes: > I recently hit an error when trying to insert into a bytea column. The > following is the first part of what appears in the Postgres log: &

[GENERAL] "invalid input syntax for type bytea"

2011-08-31 Thread Alan Millington
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 trying

Re: [GENERAL] When is an explicit cast necessary?

2010-04-14 Thread Alan Millington
ubject: Re: [GENERAL] When is an explicit cast necessary? To: "Martijn van Oosterhout" Cc: "Alan Millington" , "Alban Hertroys" , "Greg Smith" , "Postgres general mailing list" Date: Tuesday, 13 April, 2010, 20:16 Martijn van Oosterhout

Re: [GENERAL] When is an explicit cast necessary?

2010-04-10 Thread Alan Millington
nformation twice. I do not regard that as an improvement! --- On Sat, 10/4/10, Alban Hertroys wrote: From: Alban Hertroys Subject: Re: [GENERAL] When is an explicit cast necessary? To: "Alan Millington" Cc: "Greg Smith" , "Postgres general mailing list" Date: Sa

Re: [GENERAL] When is an explicit cast necessary?

2010-04-09 Thread Alan Millington
required to do so. How can such a cast be called "surprising behaviour", or produce "misleading results", to quote the first article? --- On Fri, 9/4/10, Greg Smith wrote: From: Greg Smith Subject: Re: [GENERAL] When is an explicit cast necessary? To: "Alan Millingto

[GENERAL] When is an explicit cast necessary?

2010-04-09 Thread Alan Millington
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 anot

Re: [GENERAL] Error "invalid byte sequence for encoding UTF8" on insert into BYTEA column

2010-01-23 Thread Alan Millington
>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

Re: [GENERAL] Error "invalid byte sequence for encoding UTF8" on insert into BYTEA column

2010-01-22 Thread Alan Millington
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

Re: [GENERAL] Error "invalid byte sequence for encoding UTF8" on insert into BYTEA column

2010-01-22 Thread Alan Millington
>> 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 b

[GENERAL] Error "invalid byte sequence for encoding UTF8" on insert into BYTEA column

2010-01-21 Thread Alan Millington
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 up

Re: [GENERAL] "Could not open relation XXX: No such file or directory"

2009-08-22 Thread Alan Millington
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 (assum

[GENERAL] "Could not open relation XXX: No such file or directory"

2009-08-19 Thread Alan Millington
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 2009-08

[GENERAL] plpython.dll dependencies

2009-08-12 Thread Alan Millington
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

Re: [GENERAL] Problem with Check Constraint in pg_restore

2009-07-13 Thread Alan Millington
your advice, and use EXTRACT instead, if that is going to be more robust. --- On Mon, 13/7/09, Tom Lane wrote: From: Tom Lane Subject: Re: [GENERAL] Problem with Check Constraint in pg_restore To: "Alan Millington" Cc: pgsql-general@postgresql.org Date: Monday, 13 July, 2009, 3:06

[GENERAL] Problem with Check Constraint in pg_restore

2009-07-13 Thread Alan Millington
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 we