Re: PITR Recovery and out-of-sync indexes - Mailing list pgsql-general

From Richard Huxton
Subject Re: PITR Recovery and out-of-sync indexes
Date
Msg-id 4703E390.6000200@archonet.com
Whole thread Raw
In response to Re: PITR Recovery and out-of-sync indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PITR Recovery and out-of-sync indexes
Re: PITR Recovery and out-of-sync indexes
List pgsql-general
Tom Lane wrote:
> Brian Wipf <brian@clickspace.com> writes:
>> PG tried to enforce the same LC_COLLATE and LC_CTYPE. On OS X, the
>> value of en_US.utf8 didn't exist, so I created a soft link to
>> en_US.UTF-8 in the /usr/share/locale/ directory. When I sort the
>> values of product_id_from_source on both systems using the locales in
>> this manner I get different orderings:

>> I can happily live with rebuilding indexes if this is the only
>> problem I can expect to encounter, and I would still prefer PITR over
>> replication.
>
> The whole notion scares the daylights out of me.  If you really need
> to use PITR between these two particular platforms, use a locale
> with common behavior --- C/POSIX would work.

Could you run Linux in a virtual-machine in OS X?

--
   Richard Huxton
   Archonet Ltd

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Feature Request - Defining default table space for Indexes in Conf file
Next
From: "Jimmy Choi"
Date:
Subject: Unexpected behavior with CASE statement