Re: Enabling frontend-only xlog "desc" routines - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Enabling frontend-only xlog "desc" routines
Date
Msg-id CA+Tgmob8W5DznFqP2yKMay48itu7+9f-j1iCQwMZmRfBHYRaXw@mail.gmail.com
Whole thread Raw
In response to Re: Enabling frontend-only xlog "desc" routines  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Nov 29, 2012 at 3:03 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> The other interesting question remaining is what to do about the rm_desc
>> function in rmgr.c.  We're split between these two ideas:
>
> Why try to link rmgr.c into frontend versions at all?  Just make
> a new table file that only includes the desc function pointers.
> Yeah, then there would be two table files to maintain, but it's
> not clear to me that it's uglier than these proposals ...

+1.  It's not likely to get updated very often, we can add comments to
remind people to keep them all in sync, and if you manage to screw it
up without noticing then you are adding recovery code that you have
not tested in any way whatsoever.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL
Next
From: Josh Berkus
Date:
Subject: Re: Hot Standby Feedback should default to on in 9.3+