| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "unexpected EOF" messages |
| Date: | 2012-05-03 15:06:53 |
| Message-ID: | 23823.1336057613@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Thu, May 3, 2012 at 4:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>>> Are you thinking basically "regexp against the main text", or
>>> something else, when you say "generic filter capacity"?
>> In the context of yesterday's discussions, I wonder whether a filter by
>> SQLSTATE would be appropriate.
> I'm worried it's not really granular enough.
I dislike the idea of regex-on-text because of i18n issues. There's no
guarantee for instance that all sessions are running with the same
LC_MESSAGES locale. In any case, anybody who's dead set on doing it
that way can do it today with grep.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-05-03 15:12:14 | Re: How hard would it be to support LIKE in return declaration of generic record function calls ? |
| Previous Message | Pavel Stehule | 2012-05-03 15:05:29 | Re: How hard would it be to support LIKE in return declaration of generic record function calls ? |