| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Patch to fix plpython on OS X |
| Date: | 2005-07-19 14:03:39 |
| Message-ID: | 23479.1121781819@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Jim C. Nasby" <decibel(at)decibel(dot)org> writes:
> Attached is a plpython_error_1.out file that will fix cuckoo.
What is the reason for the difference in the error message spelling
in the first place? Is this a Python version thing (and if so,
which version is newer --- that should have pride of place as
plpython_error.out I should think)? Or is there some other reason
that we need to understand more closely instead of just slapping on
a band-aid?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick Welche | 2005-07-19 15:35:03 | Re: escape string syntax and pg_dumpall |
| Previous Message | Jim C. Nasby | 2005-07-19 07:32:09 | Patch to fix plpython on OS X |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-07-19 15:23:18 | Re: COPY FROM performance improvements |
| Previous Message | Jim C. Nasby | 2005-07-19 07:32:09 | Patch to fix plpython on OS X |