| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | brook(at)biology(dot)nmsu(dot)edu |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: creating/accessing new runtime parameters |
| Date: | 2003-09-24 21:14:17 |
| Message-ID: | Pine.LNX.4.44.0309242308510.22650-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
brook(at)biology(dot)nmsu(dot)edu writes:
> As far as the general utility of it goes, I claim that it could be
> quite valuable. I am thinking of complex new datatypes (that might be
> dynamically loaded) that could benefit from having some run-time
> variables specify some aspect of their behavior. Currently, we have
> variables controlling the I/O of dates and times, for example.
> Something analogous would potentially be useful for other datatypes.
Consider it an encouragement to have your data types not duplicate any of
the various insane properties that date/time types have, imposed by the
real world.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | markw | 2003-09-24 21:22:15 | Is this a commit problem? |
| Previous Message | Doug Royer | 2003-09-24 20:04:53 | Re: [HACKERS] Announcement: planned open source billing system demonstration |