From: | DelGurth <delgurth(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Cache lookup failed for type 70385664 |
Date: | 2009-06-23 10:58:39 |
Message-ID: | 10268b3e0906230358p469c60a3mff315995da67325a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Oh, probably found the cause of the sudden restarts:
Jun 23 09:39:13 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[25239] core dumped: /var/core/core_global.postgres
Jun 23 09:45:56 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[26455] core dumped: /var/core/core_global.postgres
Jun 23 09:56:22 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[29292] core dumped: /var/core/core_global.postgres
Jun 23 10:18:00 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[3838] core dumped: /var/core/core_global.postgres
Jun 23 10:27:23 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[5653] core dumped: /var/core/core_global.postgres
Jun 23 10:38:06 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[7929] core dumped: /var/core/core_global.postgres
Jun 23 10:49:28 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[10192] core dumped: /var/core/core_global.postgres
Jun 23 10:58:59 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[12072] core dumped: /var/core/core_global.postgres
Jun 23 11:05:57 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[13262] core dumped: /var/core/core_global.postgres
Jun 23 11:18:04 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[16759] core dumped: /var/core/core_global.postgres
Jun 23 11:30:25 ph1phys01 genunix: [ID 603404 kern.notice] NOTICE: core_log:
postgres[19267] core dumped: /var/core/core_global.postgres
It's on a solaris 10 system.
pstack of the last coredump gives me:
core '/var/core/core_global.postgres' of 19267: /usr/bin/postgres -D
/postgresql/server/db_ph
080833ed slot_deform_tuple (8507718, 8560640, 8500da8, 0, 0, 8560e48) + 1a9
08500000 ???????? ()
Not sure if that's of any help though... We are running postgresql 8.2.3 on
solaris 10.
Regards,
Wessel van Norel
On Tue, Jun 23, 2009 at 12:37 PM, DelGurth <delgurth(at)gmail(dot)com> wrote:
> For a certain record in our database I'm getting cache lookup failures
> (ERROR: cache lookup failed for type 70385664). And only for one of
> the 2 array columns in that record.
>
> The table definition is:
>
> \d inhoudingen
> Table "public.inhoudingen"
> Column | Type | Modifiers
> ----------------------+-----------------------------+-----------
> verkoop_id | bigint | not null
> regel | smallint | not null
> bedrag | numeric(12,2) | not null
> berekend_op | timestamp(0) with time zone |
> berekend_bedrag | numeric(12,2) |
> comp_bedrag | numeric(12,4)[] |
> comp_naam | character varying(25)[] |
> omschrijving | character varying(100) |
> Indexes:
> "geen_dubbele_idx" PRIMARY KEY, btree (verkoop_id, regel)
> Foreign-key constraints:
> "inhoudingen_fk" FOREIGN KEY (verkoop_id) REFERENCES verkoop(id)
> ON UPDATE CASCADE ON DELETE CASCADE
> "inhoudingen_fk1" FOREIGN KEY (regel) REFERENCES regels(id) MATCH
> FULL ON UPDATE CASCADE ON DELETE RESTRICT
>
>
> And the column comp_naam is giving this error for one specific record.
>
> The database was put in shutdown mode today without a reason (as in,
> we don't know why it did that, yet) and since then it's giving this
> error.
>
> I'm now wondering what I can do to fix this. Do I need to delete that
> record, or is there a way to recover it?
>
> Regards,
> Wessel van Norel
>
From | Date | Subject | |
---|---|---|---|
Next Message | Grzegorz Jaśkiewicz | 2009-06-23 11:32:25 | Re: after vacuum analyze, explain still wrong |
Previous Message | DelGurth | 2009-06-23 10:37:04 | Cache lookup failed for type 70385664 |