Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Re: Any reason to have heap_(de)formtuple?
On Thu, 23 Oct 2008, Kris Jurka wrote: > The problem with trying to deprecate it is that the vast majority of the > backend is still using the old interfaces, so people looking for > inspiration for their external modules will likely end up using the old > interface. Like Alvaro I started this conversion a while ago, got > bored, and forgot about it. If people do want this conversion done while > keeping the old interface around, I can track down that patch, update it > and finish it up for the next CommitFest. > Here's a patch that changes everything over to the the new API and implements the old API by calling the new API. Kris Jurka
Attachment: use-new-heaptuple-api.patch.gz
Description: application/octet-stream (28.0 KB)
Description: application/octet-stream (28.0 KB)
In response to
- Re: Any reason to have heap_(de)formtuple? at 2008-10-23 19:59:56 from Kris Jurka
Responses
- Re: Any reason to have heap_(de)formtuple? at 2008-10-28 20:44:46 from Zdenek Kotala
- Re: Any reason to have heap_(de)formtuple? at 2008-11-02 01:49:17 from Tom Lane
pgsql-hackers by date
Next: From: Simon Riggs Date: 2008-10-28 00:35:52 Subject: Re: Re: [COMMITTERS] pgsql: Rework subtransaction commitprotocol for hot standby. Previous: From: Tom Lane Date: 2008-10-27 23:31:18 Subject: Re: Visibility map, partial vacuums