| From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
|---|---|
| To: | Ulf Mehlig <umehlig(at)uni-bremen(dot)de> |
| Cc: | pgsql-general(at)hub(dot)org |
| Subject: | Re: [GENERAL] NOTICE from the backend |
| Date: | 1999-05-01 12:24:30 |
| Message-ID: | 372AF27E.C4491D5@krs.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ulf Mehlig wrote:
>
> Hello PostgreSQL specialists! Short Question: What does the message
>
> "NOTICE: Rel li64_dkopf: TID 1/7: TID IN TUPLEHEADER 4/2 IS NOT THE
> SAME. TUPGONE 0."
>
> mean? Anything dangerous? (it appeared with lots of others of the same
^^^^^^^^^^^^^^^^^^
Yes.
> type after a "vacuum analyze").
As result of attempt to update 7th tuple in 1st block 2nd tuple
in 4th block will be updated. Dump/reload this table...
Seems that when I added this check I should add code to
set TID in header to valid value... -:(
Unfortunately, I don't know from where this TID difference comes
and this is very important to find it. After what operations/
assertions/FATALs you got this vacuum NOTICE?
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Constantin Teodorescu | 1999-05-01 16:17:17 | PostgreSQL on BeOS ? |
| Previous Message | Ulf Mehlig | 1999-05-01 11:24:30 | NOTICE from the backend |