Re: Dropping schemas and "illegal seek"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Felix Finch <felix(at)crowfix(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Dropping schemas and "illegal seek"
Date: 2004-06-06 22:54:58
Message-ID: 21589.1086562498@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Felix Finch <felix(at)crowfix(dot)com> writes:
> changed to
> psql -c 'DROP SCHEMA x1 CASCADE' -c 'DROP SCHEMA x2 CASCADE' ...

AFAICT psql will only execute the last -c string if you try to specify
more than one on the command line, so the above is pretty hopeless anyway,
but

> and began getting this complaint from psql:
> Can't drop schemas: Illegal seek

I don't see this here. What platform is this on, and what PG version?

> Have I hosed this database?

AFAICT whatever this is is local to psql's command processing, so no
your database isn't hosed.

My guess is that the "Illegal seek" message is coming from trying to
fseek stdin, but why it's trying to do that is impossible to guess
without seeing the complete command line.

Is "Can't drop schemas" coming from your script? I don't believe that
such a message text appears anywhere in psql or the backend.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Sabino Mullane 2004-06-06 22:57:42 Re: Check for prepared statement
Previous Message Jerry 2004-06-06 22:36:25 Need more speed for this query :)