2009/9/24 Mihail Nasedkin :
> Hi.
>
> I accidentally deleted pg_toast record from pg_class table that belongs to
> regular table (reltoastrelid).
>
> Now [select * from table_name] not work:
> ERROR: could not open relation with OID [oid_of_pg_toast_table]
>
> Is it possible to restore corruption?
Hi.
I accidentally deleted pg_toast record from pg_class table that belongs to
regular table (reltoastrelid).
Now [select * from table_name] not work:
ERROR: could not open relation with OID [oid_of_pg_toast_table]
Is it possible to restore corruption?
--
---
Regards,
M.Nasedkin
Mike angelo writes:
> Reindexing produced no reduction in size of the table in question, and a
> VACUUM ANALYZE VERBOSE pg_toast_293523 produced the message:
> skipping "pg_toast_293523" --- cannot vacuum indexes, views, or special
> system tables.
Issue the vacuum against the owning tab
I'm a newb to Postgres, and need some assistance with pg_toast. I'm running
PostgreSQL 8.3, and am having an issue with one of my pg_toast tables growing
at the rate of 1 GB per day. Can someone offer me some insight on
a) the functionality of the pg_toast_* tables?
b) how can I clear them o
On 10/23/07, Martin Strejc <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I've a special kind of problem with PostgreSQL 8.2.5 and I haven't
> found anything about that on your web or searchig by Google.
>
> The database slows down when more over many (cca 100 connections)
> are incoming. The problem
Hi!
I've a special kind of problem with PostgreSQL 8.2.5 and I haven't
found anything about that on your web or searchig by Google.
The database slows down when more over many (cca 100 connections)
are incoming. The problem begun the same time as the VACUUM foroze on
pg_toast.pg_toast
