From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | dbmanager <dbmanager(at)osb368(dot)nnov(dot)ru> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Vacuudb problem |
Date: | 2001-05-10 13:35:44 |
Message-ID: | 200105101335.f4ADZjd19103@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
What release are you running? My guess is that an upgrade will fix it.
> Hi,
>
> Help me please to resolve my problem. It is during vacuuming
> database .I resolved it last time in such a way: pg_dump and
> psql -e db<db.archiv. But after some days it appeared again.
> Here is messages :
>
> NOTICE: mdopen: couldn't open pg_temp.2297.4: No such file or directory
> NOTICE: RelationIdBuildRelation: smgropen(pg_temp.2297.4): No such file or directory
> NOTICE: mdopen: couldn't open pg_temp.2297.4: No such file or directory
> ERROR: cannot open relation pg_temp.2297.4
> vacuumdb: vacuum failed
>
> And one more question. Is there any way to encrease speed
> of restoring database . psql -e works about some hours for me...
>
> Thanks for any suggestions.
>
> Igor
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | John Coers | 2001-05-10 13:48:56 | Re: COPY locking |
Previous Message | ryan | 2001-05-10 13:22:56 | Re: Query not using index |