Bill Thoen <[EMAIL PROTECTED]> writes:
> The table seems fine this time, and there was no segfaulting nonsense at
> any time. But the server log was a lot more active. Whe I loaded this
> data the first time and had that corruption prroblem, there was hardly
> anything posted to the log. However
Tom Lane wrote:
If you have the time and interest, it might be worth repeating the
whole setup sequence starting from initdb. I'm speculating that
installing PostGIS might have somehow left corruption in server memory
that later manifested as the visible problem.
Tom,
I'm not sure if I did
On Sun, Jun 22, 2008 at 06:47:14PM -0400, Tom Lane wrote:
> Hmm. Unless you have reason to think that your hardware is flaky,
> I dislike writing this off as "just a glitch". I think most likely
> you got bit by a bug somewhere. Still, if we can't reproduce it
> it's gonna be mighty hard to find
Bill Thoen <[EMAIL PROTECTED]> writes:
> On Sun, Jun 22, 2008 at 02:17:47PM -0400, Tom Lane wrote:
>> Can you reproduce the problem if you import the same data into a new
>> table?
> Arrg! Looks like the first load was corrupted as you suspected.. When I
> tried it a second time, it seems to have
On Sun, Jun 22, 2008 at 02:17:47PM -0400, Tom Lane wrote:
> Hmm ... interesting but not conclusive. The most likely explanation
> for this is corrupt data on-disk, but how it got that way is unclear.
> Can you reproduce the problem if you import the same data into a new
> table?
Arrg! Looks like
On Sun, Jun 22, 2008 at 02:17:47PM -0400, Tom Lane wrote:
> Hmm ... interesting but not conclusive. The most likely explanation
> for this is corrupt data on-disk, but how it got that way is unclear.
> Can you reproduce the problem if you import the same data into a new
> table?
I'll try that and
Tom Lane wrote:
> This seems pretty suspicious to me. gcc 4.3 shouldn't have resulted in
> any major changes in system header layout. What I am wondering is if
> GEOS and GDAL have any direct dependencies on Postgres, and if so
> whether they've been updated to work with 8.3.
FWIW I compile wit
Bill Thoen <[EMAIL PROTECTED]> writes:
> Is this what you need to see? (I attached GDB to the running postgres
> process and let it continue until it crashed, and then entered 'bt' and
> this is what I got.)
Hmm ... interesting but not conclusive. The most likely explanation
for this is corrupt
