Re: Error message with plpgsql CONTINUE - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Error message with plpgsql CONTINUE
Date
Msg-id 55DC91A0.8020903@BlueTreble.com
Whole thread Raw
In response to Re: Error message with plpgsql CONTINUE  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On 8/25/15 10:50 AM, Jim Nasby wrote:
>> figuring out the cause of his problem.  Given the way the namespace data
>> structure works, I am not sure that we can realistically detect at line 8
>> that there was an instance of lab1 earlier, but perhaps we could word the
>
> Are there any other reasons we'd want to improve the ns stuff? Doesn't
> seem worth it for just this case, but if there were other nitpicks
> elsewhere maybe it is.

Thinking about this some more...

If we added a "prev_label_in_context" field to nsitem and changed how 
push worked we could walk the entire chain. Most everything just cares 
about the previous level, so I don't think it would be terribly invasive.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Commitfest remaining "Needs Review" items
Next
From: Tom Lane
Date:
Subject: Re: Error message with plpgsql CONTINUE