Sergei Koveshnikov <[EMAIL PROTECTED]> writes:
> int connect() {
I'm wondering about link conflicts with the standard system call connect().
Also, if you use syslog logging for Postgres error messages, it's
probably unwise to call openlog/closelog for yourself.
regards,
OK, I'll look at it from the cygwin end. Its interesting that
restarting postgres clears it. Although, I guess this could be a
problem in the cygwin DLL. Thanks for the very quick response!
McC
Tom Lane wrote:
Sean McCune <[EMAIL PROTECTED]> writes:
I have not run into this problem under L
Sean McCune <[EMAIL PROTECTED]> writes:
> I have not run into this problem under Linux before, but that doesn't
> mean anything. This application running under cygwin is more heavy duty
> than what I've run on Linux. So we don't know if its a general postgres
> bug or something that's only occ
Hi all,
We're running 7.4.1-3 under cygwin on Windows 2003 Server. We're going
to upgrade to the latest, but it takes some time to schedule this on the
various systems its running on. The system gets heavy usage... 43000
tiff files of about 30-40kb each have been inserted over a 3 month
perio
Hello to everyone!
I've got some troubles with C-Language Functions.
I wrote simple shared library:
/*=== dbsync.c ==*/
#include
#include
#include "postgres.h"
#include "fmgr.h"
#include "libpq-fe.h"
/*
CREATE OR REPLACE FUNCTION dbsync_delete() RETURNS int
AS
On Thu, Jun 24, 2004 at 11:38:59AM -0400, Tom Lane wrote:
> Kris Jurka <[EMAIL PROTECTED]> writes:
> > ERROR: invalid input syntax for type timestamp with time zone:
> > "0097-02-16 17:32:01 BC-08"
>
> Thanks for catching this. It never came up before because we never
> would try to output time
Kris Jurka <[EMAIL PROTECTED]> writes:
> ERROR: invalid input syntax for type timestamp with time zone:
> "0097-02-16 17:32:01 BC-08"
Thanks for catching this. It never came up before because we never
would try to output timezone info for a BC date...
We could make it output either of
I understand very well your answer, however, I would like to introduce
briefly our needs and why we decided to use the "-r no_indicator" with ECPG.
We are porting a Pro*C/Oracle 7.3.4 based application (about 4000 SQL
requests) to ECPG/PostGreSQL 7.4.2.
This application mostly uses VARCHAR varia
On Tue, 2004-06-22 at 19:23, Tom Lane wrote:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > PQexec(conn,
> >"PREPARE S123_000 (text) AS SELECT * from test1 WHERE t = $1");
> > When invoking PQexecPrepared() I get the following message from the backend
> > ERROR: prepared stateme
Dumping and restoring the regression database in cvs tip gives the
following error upon restore:
ERROR: invalid input syntax for type timestamp with time zone:
"0097-02-16 17:32:01 BC-08"
CONTEXT: COPY timestamptz_tbl, line 42, column d1: "0097-02-16 17:32:01
BC-08"
Kris Jurka
The following bug has been logged online:
Bug reference: 1182
Logged by: Damien Guitard
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Linux Redhat 7.2
Description:Index choice
Details:
Hi,
(sorry for my english)
I've seen a differen
11 matches
Mail list logo
