Mats Lofkvist <[EMAIL PROTECTED]> 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 r
[EMAIL PROTECTED] (Andrew Sullivan) writes:
> On Thu, Jul 11, 2002 at 11:15:42PM -0400, Tom Lane wrote:
> > Mats Lofkvist <[EMAIL PROTECTED]> writes:
> > > When testing postgres 7.2.1 on a sparc/solaris8 box with
> > > --enable-locale --enable-multibyte I get a crash in
> > > convert_string_datum.
On Thu, Jul 11, 2002 at 11:15:42PM -0400, Tom Lane wrote:
> Mats Lofkvist <[EMAIL PROTECTED]> writes:
> > When testing postgres 7.2.1 on a sparc/solaris8 box with
> > --enable-locale --enable-multibyte I get a crash in
> > convert_string_datum.
>
> This smells like a problem that we chased down a
Tom Lane wrote:
> Mats Lofkvist <[EMAIL PROTECTED]> writes:
> > When testing postgres 7.2.1 on a sparc/solaris8 box with
> > --enable-locale --enable-multibyte I get a crash in
> > convert_string_datum.
>
> This smells like a problem that we chased down awhile back, that
> snprintf on Solaris is
Mats Lofkvist <[EMAIL PROTECTED]> writes:
> When testing postgres 7.2.1 on a sparc/solaris8 box with
> --enable-locale --enable-multibyte I get a crash in
> convert_string_datum.
This smells like a problem that we chased down awhile back, that
snprintf on Solaris is broken (it will write past the
Hi,
When testing postgres 7.2.1 on a sparc/solaris8 box with
--enable-locale --enable-multibyte I get a crash in
convert_string_datum.
The backend just dies when doing an select. With casserts
and debug configured in I got the following in the log:
NOTICE: AllocSetFree: detected write past c
