Re: obsolete code - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: obsolete code
Date
Msg-id 510BE80A.1060904@dunslane.net
Whole thread Raw
In response to Re: obsolete code  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: obsolete code  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: obsolete code  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: obsolete code  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On 02/01/2013 10:38 AM, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.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




pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Streaming-only cascading replica won't come up without writes on the master
Next
From: Pavan Deolasee
Date:
Subject: Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker)