Обсуждение: Error log fillingup

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

On 09/09/2009 09:27, Chris Leahy 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'.

That may well be the problem - a query is referring to a column called
"options" which as you've said doesn't exist, hence the error message.

I've also seen this when a string value isn't quoted, e.g. -

  insert into (....) values ('abc', options, ...) ...

When this happens the server thinks that the query is taking the value
of a column called 'options', instead of the literal value 'options'.

Ray.

------------------------------------------------------------------
Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
rod@iol.ie
Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals
------------------------------------------------------------------

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@mystrata.com.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>