Re: Error log fillingup

From: Korry <korry(dot)douglas(at)enterprisedb(dot)com>
To: "cleahy(at)mystrata(dot)com(dot)au" <cleahy(at)mystrata(dot)com(dot)au>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Error log fillingup
Date: 2009-09-09 09:35:18
Message-ID: 1AA2B0E8-3863-4734-AE42-98DB02394BCC@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


That query looks suspiciously similar to a SQL Server (Sybase or
Microsoft) query.

@@options is the name of a SQL Server global variable. It looks like
your client application thinks that it is connected to a copy of SQL
Server, not Postgres.

-- Korry

On Sep 9, 2009, at 4:27 AM, Chris Leahy <cleahy(at)mystrata(dot)com(dot)au> wrote:

> Hi All
>
> I'm running postgreSQL 7.3 on 2 installations, both with the same
> problem.
>
> The error logs for both installations are filling up with the
> following;
>
> ESTERROR: 42703: column "options" does not exist
> ESTLOCATION: transformColumnRef, parse_expr.c: 396
> ESTSTATEMENT: select @@options
>
> This has become a real nuisance.
> I have not defined a table 'options' and non of the tables I have
> defined have a column called 'options'.
> I am not aware of this call being made, but it is filling up the
> error logs at an alarming rate.
>
> All connections to the databases are through unixODBC.
>
> I hope someone can shine some light on this problem. It would have
> to be affecting the performance of the DB.
> The DB's have been running for a few years and appear to be stable.
> Just this error reoccurring.
> My concern is that it could mask a real error when it happens.
>
> Many thanks <stock_smiley-3.png>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Berge Schwebs Bjørlo 2009-09-09 10:17:33 WAL archiving file name collision
Previous Message Raymond O'Donnell 2009-09-09 08:54:08 Re: Error log fillingup