Bruce Momjian <br...@momjian.us> writes: > ! ereport(ERROR, > ! > (ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE, > ! errmsg("cannot perform FREEZE > because of previous table activity in the current transaction")));
[ itch... ] What is "table activity"? I always thought of tables as being rather passive objects. And anyway, isn't this backwards? What we're complaining of is *lack* of activity. I don't see why this isn't using the same message as the other code path, namely > + ereport(ERROR, > + (ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE, > + errmsg("cannot perform FREEZE because the > table was not created or truncated in the current transaction"))); regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers