Re: Add LINE: hint when schemaname.typename is a non-existent schema - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Add LINE: hint when schemaname.typename is a non-existent schema
Date
Msg-id CA+Tgmoav45qnftyw0BmkAwPz4kPJj+aFzbet5-o3+cHnG--ksA@mail.gmail.com
Whole thread Raw
In response to Add LINE: hint when schemaname.typename is a non-existent schema  (Ryan Kelly <rpkelly22@gmail.com>)
List pgsql-hackers
On Mon, Feb 2, 2015 at 2:44 PM, Ryan Kelly <rpkelly22@gmail.com> wrote:
> The attached patch adds a LINE: ... hint when schemaname.typename
> results in a schema which does not exist. I came across this when a
> missing comma in a SELECT list resulted in an error without a location
> in a query a few thousand lines long.
>
> Before:
>
> (postgres@[local]:5432 14:41:25) [postgres]> select test.id 'all' as
> example from test;
> ERROR:  3F000: schema "test" does not exist
> LOCATION:  get_namespace_oid, namespace.c:2826
>
> After:
>
> (postgres@[local]:5433 14:42:32) [postgres]> select test.id 'all' as
> example from test;
> ERROR:  3F000: schema "test" does not exist
> LINE 1: select test.id 'all' as example from test;
>                ^
> LOCATION:  LookupTypeName, parse_type.c:171
>
> -Ryan Kelly

Please add your patch to
https://commitfest.postgresql.org/action/commitfest_view/open so do we
don't forget about it.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Redesigning checkpoint_segments
Next
From: Andres Freund
Date:
Subject: Re: Getting rid of wal_level=archive and default to hot_standby + wal_senders