Why does pg_ctl.c have its own copy of PM_VERSIONSTR? - Mailing list pgsql-hackers

From Tom Lane
Subject Why does pg_ctl.c have its own copy of PM_VERSIONSTR?
Date
Msg-id 16177.1203541065@sss.pgh.pa.us
Whole thread Raw
Responses Re: Why does pg_ctl.c have its own copy of PM_VERSIONSTR?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Why isn't pg_ctl.c using PG_VERSIONSTR from miscadmin.h?  Seems like
this is something that will have to be kept in sync manually (I see
from the CVS logs that Peter already had to do that once).

If the feeling is that miscadmin.h is a backend include file that
shouldn't be used by pg_ctl (which is not totally unreasonable,
though I think there's no harm in it given the current contents
of that file), maybe we should move PG_VERSIONSTR someplace else?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Permanent settings
Next
From: "Heikki Linnakangas"
Date:
Subject: Re: Which MemoryContext?