PostgreSQL Discussion - Error migrating from 7.4.3 to 8.0.3

Author

Error migrating from 7.4.3 to 8.0.3

Raj Gupta

2005-09-26, 1:24 pm

Hi,

We are trying to migrate our database from 7.4.3 of Postgresql to
8.0.3.

While migrating a table, we got the following error:

ERROR: could not write block 2830 of relation 1663/2276041/4965853:
Operation not permitted

This came when pg was trying to create an index on the relation. Has
anyone seen this behavior before? Are we doing something wrong?

Thanks

Raj

--
Raj Gupta_ _ _ _ _ _ _ _ _ _ _ gupta@zeesource.net
1684 Nightingale Avenue _ __Suite 201
Sunnyvale, CA 94087_ _ _ _ 408-733-2737(fax)

http://www.zeesource.net

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Poul Møller Hansen

2005-09-26, 1:24 pm

Raj Gupta wrote:
> Hi,
>
> We are trying to migrate our database from 7.4.3 of Postgresql to 8.0.3.
>
> While migrating a table, we got the following error:
>
> ERROR: could not write block 2830 of relation 1663/2276041/4965853:
> Operation not permitted
>
> This came when pg was trying to create an index on the relation. Has
> anyone seen this behavior before? Are we doing something wrong?
>

Have you dumped and restored the database ?
The structure of the two major versions is not compatible.

Poul

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Vivek Khera

2005-09-26, 1:24 pm

On Sep 26, 2005, at 12:43 PM, Raj Gupta wrote:

> While migrating a table, we got the following error:
>
> ERROR: could not write block 2830 of relation
> 1663/2276041/4965853: Operation not permitted
>
> This came when pg was trying to create an index on the relation.
> Has anyone seen this behavior before? Are we doing something wrong?
>

This is during the pg_restore step when loading your data into the
8.0.3 instance? it looks suspiciously like some sort of low-level
fault. Try running some hardware diags on your system.

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Raj Gupta

2005-09-26, 1:24 pm

Yes, I followed the procedure for dumping and restoring binary data (to
include large objects).

It creates all the tables, etc. fine, and all the other indices are
created. It's just this one index that it gives me a problem.

The problem also happens if I manually try to create the same index on
that table. Otherwise, everything else seems to be okay.

Raj

On Sep 26, 2005, at 10:09 AM, Poul Møller Hansen wrote:

> Raj Gupta wrote:
>
> Have you dumped and restored the database ?
> The structure of the two major versions is not compatible.
>
> Poul
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Raj Gupta

2005-09-26, 8:24 pm

This is both while doing a pg_restore and also when doing a 'create
index' command.

This is running on Mac OS X 10.3

Postgresql 7.4 runs fine, and creates the index, so I would be
surprised if this is a hardware error?

Raj

On Sep 26, 2005, at 10:23 AM, Vivek Khera wrote:

>
> On Sep 26, 2005, at 12:43 PM, Raj Gupta wrote:
>
>
> This is during the pg_restore step when loading your data into the
> 8.0.3 instance? it looks suspiciously like some sort of low-level
> fault. Try running some hardware diags on your system.
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: explain analyze is your friend

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql
.org so that your
message can get through to the mailing list cleanly

Tom Lane

2005-09-26, 8:24 pm

Raj Gupta <gupta@zeesource.net> writes:
> Postgresql 7.4 runs fine, and creates the index, so I would be
> surprised if this is a hardware error?

"Operation not permitted" during a write() is not very sensible;
the kernel should have complained when the file was open()'d if there
were permission issues. So I'd say there is something pretty broken
about either your kernel or the filesystem the database is on.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Raj Gupta

2005-09-26, 8:24 pm

This is a stock Mac OS 10.3 (Panther). Has anyone else seen this
problem with 8.0.3 on Panther?

According to the INSTALL file 10.3 should work fine, as reported by
Andrew Rawnsley, cc'd on this message.

Raj

On Sep 26, 2005, at 12:23 PM, Tom Lane wrote:

> "Operation not permitted" during a write() is not very sensible;
> the kernel should have complained when the file was open()'d if there
> were permission issues. So I'd say there is something pretty broken
> about either your kernel or the filesystem the database is on.
>
> regards, tom lane

ERROR: could not write block 2830 of relation 1663/2276041/4965853:
Operation not permitted

This came when pg was trying to create an index on the relation.

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Sponsored Links