Well, first thing I'd ask is whether the other installation is using
the same locale settings.
Oh, yes, I am very sure of that.
Mike
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Wed, May 28, 2003 at 09:04:18AM -0400, Michael Brusser wrote:
Well, first thing I'd ask is whether the other installation is using
the same locale settings.
Oh, yes, I am very sure of that.
Note that while the machine reports the C locale, pg_controldata
actually said the database was
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Tom Lane
Sent: Sunday, May 25, 2003 9:03 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] vacuum analyze corrupts database
Michael Brusser [EMAIL PROTECTED] writes:
(dbx) where 30
=[1] pfree(0x489420, 0xffbee890
Michael Brusser [EMAIL PROTECTED] writes:
but do you rule out any problems in Postgres code?
Never ... but when you're the only one reporting a problem, a local
issue is something to consider.
Is there a good explanation to why the same table loaded into another
Postgres
installation on the
