Tom Lane wrote: > On second thought, I think it *could* lead to a visible failure. > Suppose the OID counter wraps around and the OID that had been used for > the temporary CLUSTER table gets assigned to a new table. If that table > needs a toast table, it'll try to create one using the name that is > already in use. We have defenses against picking an OID that's in use, > but none for toast table names. So I think it's indeed worth fixing.
Okay, I'll see to it after committing this autovacuum stuff. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers