Re: export FUNC_MAX_ARGS as a read-only GUC variable

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Kris Jurka <books(at)ejurka(dot)com>, Alex <alex(at)meerkatsoft(dot)com>, "Lada 'Ray' Lostak" <ray(at)unreal64(dot)net>, pgsql-patches(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: export FUNC_MAX_ARGS as a read-only GUC variable
Date: 2003-12-01 06:27:03
Message-ID: 16051.1070260023@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-patches

Joe Conway <mail(at)joeconway(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Robert Treat 2003-12-01 06:31:38 Re: PostgreSQL Advocacy, Thoughts and Comments
Previous Message Joe Conway 2003-12-01 06:22:51 Re: export FUNC_MAX_ARGS as a read-only GUC variable

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2003-12-01 10:48:40 Re: clock_timestamp() and transaction_timestamp() function
Previous Message Joe Conway 2003-12-01 06:22:51 Re: export FUNC_MAX_ARGS as a read-only GUC variable