Re: tuplesort_gettuple_common() and *should_free argument - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: tuplesort_gettuple_common() and *should_free argument
Date
Msg-id CAM3SWZSu8ey48y7vky_k5UTVSYu77cS2Fuhb+k+WTTC4KNp0SQ@mail.gmail.com
Whole thread Raw
In response to Re: tuplesort_gettuple_common() and *should_free argument  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: tuplesort_gettuple_common() and *should_free argument  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] tuplesort_gettuple_common() and *should_free argument  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Dec 7, 2016 at 11:55 PM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> Should we be worried about breaking the API of tuplesort_get* functions?
> They might be used by extensions. I think that's OK, but wanted to bring it
> up. This would be only for master, of course, and any breakage would be
> straightforward to fix.

I don't think so. I'm not aware of any third party extensions that
call tuplesort.c routines, despite having looked for them. I noticed
that pg_repack doesn't. For any that do, they'll break in a
predictable, obvious way.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Parallel execution and prepared statements
Next
From: Stephen Frost
Date:
Subject: Re: pg_dump vs. TRANSFORMs