Postgres Pro
Downloads
Home   >   mailing lists

Re: export FUNC_MAX_ARGS as a read-only GUC variable - Mailing list pgsql-patches

From Tom Lane
Subject Re: export FUNC_MAX_ARGS as a read-only GUC variable
Date
Msg-id 16051.1070260023@sss.pgh.pa.us
Whole thread Raw
In response to Re: export FUNC_MAX_ARGS as a read-only GUC variable  (Joe Conway <mail@joeconway.com>)
List pgsql-patches
Tree view 
Joe Conway <mail@joeconway.com> writes:
> It will require an initdb -- should I hold off for other
> pending changes also requiring initdb?

No, there's no particular reason to avoid initdbs during development
cycles.  That's why we have catversion in the first place ...

            regards, tom lane

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Re: export FUNC_MAX_ARGS as a read-only GUC variable
Next
From: Peter Eisentraut
Date:
Subject: Re: clock_timestamp() and transaction_timestamp() function