ERROR: cache lookup failed for type 14237017

From: Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: ERROR: cache lookup failed for type 14237017
Date: 2010-09-21 20:07:12
Message-ID: AANLkTi==HPcmVnP_qPRNmp+Ay01N_NPRo65G5__qX7qf@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yesterday, I had twelve thousand "cache lookup failed for type N"
messages, like this:

2010-09-20 00:00:00 PDT ERROR: cache lookup failed for type 14237017
2010-09-20 00:00:00 PDT CONTEXT: SQL statement "INSERT INTO
mycluster.sl_log_2 (log_origin, log_xid, log_tableid, log_actionseq,
log_cmdtype, log_cmddata) VALUES (1, $1, $2,
nextval('mycluster.sl_action_seq'), $3, $4);"

The context is always Slony sl_log_2 table. All twelve thousand
errors occurred within 40 minutes. This did happen right after a
Slony cluster set drop and recreate.

What does "type 14237017" mean? What cache are we talking about?

I am concerned because this is classified as ERROR rather than WARNING.

Thanks,
Aleksey

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tomas Vondra 2010-09-21 20:38:24 Re: pg_relation_size / could not open relation with OID #
Previous Message Rhys A.D. Stewart 2010-09-21 19:56:10 versioned pl/pgsql functions