| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New error code to track unsupported contexts |
| Date: | 2015-04-07 22:42:34 |
| Message-ID: | 55245D5A.5000500@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/28/14 11:41 PM, Michael Paquier wrote:
> Hi all,
>
> When pg_event_trigger_dropped_objects is run in a context that is not
> the one of an event trigger, currently the error code
> ERRCODE_FEATURE_NOT_SUPPORTED is returned. Wouldn't it be better to
> have an error to define an out-of-context instead? It seems that it
> would be a good thing to have more error verbosity for situations like
> the case above. Note that this idea has been mentioned on this ML a
> couple of weeks back. In any case, attached is a patch showing the
> idea.
>
> Opinions? Is that worth having?
Anything ever happen with this? (FWIW, I'm in favor of it. Reporting the
feature isn't supported is confusing...)
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-04-07 22:44:07 | Re: EvalPlanQual behaves oddly for FDW queries involving system columns |
| Previous Message | Jim Nasby | 2015-04-07 22:39:32 | Re: Replication identifiers, take 4 |