Search Postgresql Archives

Re: PITR Recovery and out-of-sync indexes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Richard Huxton wrote:
> Tom Lane wrote:
>> Brian Wipf <brian@xxxxxxxxxxxxxx> 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?

I think it would be easier (and more performant) to define a new locale
on OS/X (or on Linux) to match the behavior of the other system.
(Perhaps define a new locale on both, with matching name and matching
behavior).

-- 
Alvaro Herrera                        http://www.advogato.org/person/alvherre
"No hay hombre que no aspire a la plenitud, es decir,
la suma de experiencias de que un hombre es capaz"

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux