From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Brian Wipf <brian(at)clickspace(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: PITR Recovery and out-of-sync indexes |
Date: | 2007-10-03 18:46:40 |
Message-ID: | 4703E390.6000200@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Brian Wipf <brian(at)clickspace(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-10-03 18:59:06 | Re: PITR Recovery and out-of-sync indexes |
Previous Message | Tom Lane | 2007-10-03 18:40:12 | Re: Feature Request - Defining default table space for Indexes in Conf file |