| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mats Lofkvist <mal(at)algonet(dot)se> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: 7.2.1 backend crash (convert_string_datum, locale) |
| Date: | 2002-07-15 13:56:15 |
| Message-ID: | 16056.1026741375@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Mats Lofkvist <mal(at)algonet(dot)se> writes:
> Without neither --enable-locale or --enable-multibyte it
> seems to work, but as I had to create a new database when
> removing locale any problems local to the first database
> are not seen anymore.
Hm. If the database is already corrupt then simply recompiling
a corrected binary isn't going to magically make things perfect.
Maybe you should retry the snprintf patch and/or --enable-multibyte
using fresh databases.
> Is postgres 8-bit clean without locale support enabled?
> (I don't care about sort orders and such, only need to
> read/write 8-bit chars via jdbc).
In that case you don't really need locale, no. Not sure about
whether you need multibyte; does JDBC expect Unicode support?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-07-15 20:43:53 | Re: Unable to install postgres on Mips platform. |
| Previous Message | Mats Lofkvist | 2002-07-15 12:59:19 | Re: 7.2.1 backend crash (convert_string_datum, locale) |