quot;checkpoint_segments".
. . .
(lots of checkpoints static with the COPY loading, but otherwise things
looked normal from here on.)
So I think postgres is all right, but I'm not so sure about postgis. I
did have problems trying to compile GEOS (and GDAL) so maybe that's
where
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
t one of the main things you have to teach people is how
to use GDB. ;-)
Thanks, Tom! I really appreciate your help.
- Bill Thoen
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
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:
Bill Thoen <[EMAIL PROTECTED]> writes:
Does anyone know what happened and how I can fix it?
Well, you evidently hit a bug, but there's not nearly enough info here
to guess whether the bug is in Postgres, PostGIS, GEOS, or GDAL, or
perhaps in your custom bu
