| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Andrew Chernow <ac(at)esilo(dot)com> |
| Cc: | Warren Turkal <turkal(at)google(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: timestamp datatype cleanup |
| Date: | 2008-03-09 18:27:54 |
| Message-ID: | 20080309182754.GA25745@feivel.credativ.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> >> As long as both implementations are kept in sync I don't see a reason.
>
> Sharing the backend data type converters with client stuff is an obvious
> win, but its a tedious process probably lacking any motivation. We did
> look at it though, it is possible.
I thought we were just talking about some definitions. If we were to
move the whole logic into one place we might be facing a
performance penalty inside the backend, maybe not a large one though.
Others around here are better suited to judge this.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Chernow | 2008-03-09 19:37:21 | Re: timestamp datatype cleanup |
| Previous Message | Tom Lane | 2008-03-09 18:25:15 | Re: Lazy constraints / defaults |