| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: obsolete code |
| Date: | 2013-02-01 16:06:34 |
| Message-ID: | 510BE80A.1060904@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/01/2013 10:38 AM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> fmgr.c contains this:
>> * DEPRECATED, DO NOT USE IN NEW CODE
>> Should we just drop all support for the old interface now?
> Is there any actual benefit to removing it? I don't recall that
> it's been the source of any maintenance burden. I'd be fine with
> dropping it if it were costing us something measurable, but ...
>
>
My hope was that if we got rid of the old stuff we wouldn't need to use
PG_FUNCTION_INFO_V1(myfunc);
in external modules any more (I recently got bitten through forgetting
this and it cost me an hour or two).
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2013-02-01 16:16:38 | Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker) |
| Previous Message | Pavan Deolasee | 2013-02-01 15:54:33 | Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker) |