Skip site navigation (1) Skip section navigation (2)

pgsql: Make ExecEvalFieldSelect throw a more intelligible error if it's

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Make ExecEvalFieldSelect throw a more intelligible error if it's
Date: 2010-01-09 20:46:19
Message-ID: 20100109204619.60E8D7541B9@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Make ExecEvalFieldSelect throw a more intelligible error if it's asked to
extract a system column, and remove a couple of lines that are useless
in light of the fact that we aren't ever going to support this case.  There
isn't much point in trying to make this work because a tuple Datum does
not carry many of the system columns.  Per experimentation with a case
reported by Dean Rasheed; we'll have to fix his problem somewhere else.

Modified Files:
--------------
    pgsql/src/backend/executor:
        execQual.c (r1.259 -> r1.260)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execQual.c?r1=1.259&r2=1.260)

pgsql-committers by date

Next:From: Robert HaasDate: 2010-01-10 01:23:08
Subject: pgsql: Document pg_tablespace.spcoptions.
Previous:From: Robert HaasDate: 2010-01-09 18:06:47
Subject: Re: pgsql: Also update ChangerLog file.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group