Ack. I meant 9.1.4:
~ ∴ psql
psql (9.1.4)
Thanks.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/SQLSTATE-XX000-Internal-Error-7-tp5682117p5721842.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (p
On 08/30/2012 10:24 AM, johnkeefe wrote:
I know this post is a few months old now, but I have a strikingly similar
setup and am getting a similar, somewhat more reliable error:
ERROR: could not open file "base/29292/12186914_fsm": Invalid argument
It happens while doing an ST_Difference() f
I know this post is a few months old now, but I have a strikingly similar
setup and am getting a similar, somewhat more reliable error:
ERROR: could not open file "base/29292/12186914_fsm": Invalid argument
It happens while doing an ST_Difference() function on two large geometries.
I'm runnin
Ben Madin writes:
> On 03/05/2012, at 11:57 AM, Tom Lane wrote:
>> So this is smelling like a kernel or filesystem bug. I wonder exactly
>> which OS X update you're running, and what sort of filesystem the
>> database is stored on.
> [ it's an up-to-date, pretty vanilla looking OS X Lion install
On Thu, May 03, 2012 at 02:46:16PM +0800, Ben Madin wrote:
> (PS How did you come to deciding that it was EINVAL - is that 'Error INVALid
> argument'?)
It's one of the standard error codes, see for example
http://www.jbox.dk/sanos/source/include/errno.h.html
Tom is right, it's not clear how this
G'day Tom,
On 03/05/2012, at 11:57 AM, Tom Lane wrote:
> Ben Madin writes:
>> SQLSTATE[XX000]: Internal error: 7 ERROR: could not open file
>> "base/102979/430122_fsm": Invalid argument
>
> [ scratches head ... ] AFAICS the only documented reason for open() to
> fail with EINVAL on OS X is
Ben Madin writes:
> SQLSTATE[XX000]: Internal error: 7 ERROR: could not open file
> "base/102979/430122_fsm": Invalid argument
[ scratches head ... ] AFAICS the only documented reason for open() to
fail with EINVAL on OS X is
[EINVAL] The value of oflag is not valid.
which is
G'day all,
I'm going to go slowly on this, but I am intermittently (as in sometimes the
query works fine, sometimes it stops after 5 minutes and I get the message)
receiving the error message below on a long running query that is populating a
newly created table with a PostGIS Geometry column.
