Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-04 Thread Tom Lane
Simon Riggs <[EMAIL PROTECTED]> writes: > On Thu, 2007-10-04 at 09:21 -0600, Brian Wipf wrote: >> The Apple Xserve is easy to maintain and rock solid reliable. If it >> had better performance to its Fibre Channel RAID array, it would be a >> better main server too. The Linux box is a better per

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-04 Thread Simon Riggs
On Thu, 2007-10-04 at 09:21 -0600, Brian Wipf wrote: > On 4-Oct-07, at 8:14 AM, Simon Riggs wrote: > > The First Commandment is Make Thy Servers Identical, which applies to > > OS, OS version, disk layouts/config as well as basic hardware. If > > they're not then you're going to get some strange re

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-04 Thread Brian Wipf
On 4-Oct-07, at 8:14 AM, Simon Riggs wrote: The First Commandment is Make Thy Servers Identical, which applies to OS, OS version, disk layouts/config as well as basic hardware. If they're not then you're going to get some strange results. Other than the corrupt indexes on varchar columns, there

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-04 Thread Simon Riggs
On Tue, 2007-10-02 at 17:11 -0600, Brian Wipf wrote: > Both servers have identical Intel processors and both are running 64- > bit PostgreSQL 8.2.4. The original server is running 64-bit openSUSE > 10.2 (Linux 2.6.18.2-34-default #1 SMP Mon Jul 16 01:16:32 GMT 2007 > x86_64 x86_64 x86_64 GNU/

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-03 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > Richard Huxton wrote: >> 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 bot

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-03 Thread Alvaro Herrera
Richard Huxton wrote: > Tom Lane wrote: >> Brian Wipf <[EMAIL PROTECTED]> 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

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-03 Thread Richard Huxton
Brian Wipf wrote: On 3-Oct-07, at 12:46 PM, Richard Huxton wrote: Could you run Linux in a virtual-machine in OS X? That's an idea. Performance-wise though, I think we'd be better off wiping OS X and installing Linux. As an added bonus, we'll be able to get way better performance out of our

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-03 Thread Brian Wipf
On 3-Oct-07, at 12:46 PM, Richard Huxton wrote: Tom Lane wrote: Brian Wipf <[EMAIL PROTECTED]> 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 so

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-03 Thread Richard Huxton
Tom Lane wrote: Brian Wipf <[EMAIL PROTECTED]> 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 s

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-03 Thread Tom Lane
Brian Wipf <[EMAIL PROTECTED]> 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 usi

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-03 Thread Brian Wipf
On 3-Oct-07, at 8:07 AM, Tom Lane wrote: PG 8.2 does store data in the pg_control file with which it can check for the most common disk-format-incompatibility problems (to wit, endiannness, maxalign, and --enable-integer-datetimes). If Brian has stumbled on another such foot-gun, it'd be good to

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-03 Thread Tom Lane
Richard Huxton <[EMAIL PROTECTED]> writes: > Brian Wipf wrote: >> Both servers have identical Intel processors and both are running 64-bit >> PostgreSQL 8.2.4. The original server is running 64-bit openSUSE 10.2 >> (Linux 2.6.18.2-34-default #1 SMP Mon Jul 16 01:16:32 GMT 2007 x86_64 >> x86_64 x

Re: [GENERAL] PITR Recovery and out-of-sync indexes

2007-10-03 Thread Richard Huxton
Brian Wipf wrote: We are running a production server off of a new database that was synchronized using PITR recovery. We found that many of the btree indexes were out of sync with the underlying data after bringing the new server out of recovery mode, but the data itself appeared to be okay.

[GENERAL] PITR Recovery and out-of-sync indexes

2007-10-02 Thread Brian Wipf
We are running a production server off of a new database that was synchronized using PITR recovery. We found that many of the btree indexes were out of sync with the underlying data after bringing the new server out of recovery mode, but the data itself appeared to be okay. Both servers h