Re: [GENERAL] Strange Postgresql behavior solved

2008-07-26 Thread owen hartnett
On Jul 26, 2008, at 2:32 AM, "Leif B. Kristensen" <[EMAIL PROTECTED]> wrote: On Saturday 26. July 2008, Owen Hartnett wrote: Probably some funky stuff with the router (not one of their expensive ones) that caused all the consternation, but I originally thought corrupt database (because I co

Re: [GENERAL] Strange Postgresql behavior solved

2008-07-25 Thread Leif B. Kristensen
On Saturday 26. July 2008, Owen Hartnett wrote: >Probably some funky stuff with the router (not one of their expensive >ones) that caused all the consternation, but I originally thought >corrupt database (because I could get 117 records to come out fine, >but not the 118th). Also, I had narrowed i

Re: [GENERAL] Strange Postgresql behavior solved

2008-07-25 Thread Tom Lane
Owen Hartnett <[EMAIL PROTECTED]> writes: > I spent a day on this, and it's really not a PostgreSQL issue, but I > thought I'd post it in case someone else comes down with it. > Scenario: > I moved the physical location and networking environment of the > server. It's on Mac OS X - XServe, but

[GENERAL] Strange Postgresql behavior solved

2008-07-25 Thread Owen Hartnett
I spent a day on this, and it's really not a PostgreSQL issue, but I thought I'd post it in case someone else comes down with it. Scenario: I moved the physical location and networking environment of the server. It's on Mac OS X - XServe, but that isn't germaine to the story. Originally,