| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gerhard Heift <ml-postgresql-20081012-3518(at)gheift(dot)de> |
| Cc: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PANIC: hash table "LOCK" hash corrupted |
| Date: | 2009-10-04 19:10:08 |
| Message-ID: | 23206.1254683408@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Gerhard Heift <ml-postgresql-20081012-3518(at)gheift(dot)de> writes:
> I'm playing with postgres in OpenVZ. When I migrate my machine with
> the database from one host to another I get following errors:
> 2009-10-04 20:20:43 CEST PANIC: hash table "LOCK hash" corrupted
> 2009-10-04 20:20:43 CEST STATEMENT: begin
> 2009-10-04 20:20:43 CEST @ LOG: server process (PID 14554) was
> 2009-10-04 20:20:43 CEST @ LOG: terminating any other active server processes
> What does this mean?
Apparently it means that OpenVZ doesn't work too well :-( --- it
hasn't migrated the contents of shared memory accurately. This
could be a synchronization type of problem, eg contents of process
local memory and shared memory not copied at the same instant.
IIRC one of the main reasons for "hash table corrupted" panics is
failing to find a hash table entry that is expected to be there
according to some other state information.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2009-10-04 19:38:14 | Re: How useful is the money datatype? |
| Previous Message | Gerhard Heift | 2009-10-04 18:30:39 | PANIC: hash table "LOCK" hash corrupted |