| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, 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> |
| Subject: | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: |
| Date: | 2003-11-30 19:08:29 |
| Message-ID: | Pine.LNX.4.44.0311302007030.11144-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토 커뮤니티SQL pgsql-patches |
Tom Lane writes:
> One could make a good case that INDEX_MAX_KEYS should be exported along
> with FUNC_MAX_ARGS, rather than letting people write client code that
> assumes they are the same.
You can determine these values by looking into the system catalogs.
> I was intending to propose that we also export the following as
> read-only variables:
> * NAMEDATALEN
And this as well.
> * BLCKSZ
Why would anyone be interested in that?
> * integer-vs-float datetime flag
Here we should really decide on one representation in the near term.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-11-30 19:34:34 | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question) |
| Previous Message | Peter Eisentraut | 2003-11-30 19:05:53 | Re: pg_hba.conf problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-11-30 19:10:01 | Re: Problem with dblink |
| Previous Message | Tom Lane | 2003-11-30 18:56:06 | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question) |