| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Joseph Shraibman <joseph(at)xtenit(dot)com>, nolan(at)celery(dot)tssi(dot)com, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: fomatting an interval |
| Date: | 2003-05-13 04:55:48 |
| Message-ID: | 5997.1052801748@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> Given that recompiling and adding the new tuple into pg_proc by means of
> a simple INSERT(*) should be enough, it's hardly necessary to force an
> initdb.
> (*) It _can_ be done, right?
I think so. The critical point is that interval_scale is not in the
compiled-in table of known internal functions in 7.3.2. A recompile
with the added pg_proc.h line should get it in there, and then you could
manually add the pg_proc entry without actually doing initdb. But I
haven't tested it to be sure there are no gotchas.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim GUNDUZ | 2003-05-13 05:57:56 | Re: .NET and PostgreSQL |
| Previous Message | Alvaro Herrera | 2003-05-13 04:29:22 | Re: fomatting an interval |