Bill Thoen <bthoen(at)gisnet(dot)com> 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, this time I noticed when I ran the
> postgis script that there was some weirdness written to the log that
> doesn't look right . Does this look like geos or postgis is a bit broken
> to you?
No, that's more or less the sort of output I'd expect to see from
loading the postgis datatypes. There's nothing wrong here that I can
So, whatever that glitch was, it seems we don't know how to trigger it.
Oh well ...
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Bruce Momjian||Date: 2008-06-23 19:50:16|
|Subject: Re: BUG #4027: backslash escaping not disabled in
|Previous:||From: Bill Thoen||Date: 2008-06-23 14:58:15|
|Subject: Re: Abnormal termination of PostgreSQL|