From: | Jeff Frost <jeff(at)pgexperts(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #13968: invalid page in block error |
Date: | 2016-02-17 17:27:41 |
Message-ID: | 0A0D5C60-FF93-474C-886F-8AB35D038F6D@pgexperts.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> On Feb 17, 2016, at 8:37 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> jeff(at)pgexperts(dot)com writes:
>> We ran into this error on 9.4.5 this morning:
>
>> 2016-02-17 03:32:49.598
>> GMT,"procore_db","procore",22743,"10.232.0.19:59846",56c3df6e.58d7,3,"UPDATE",2016-02-17
>> 02:48:14 GMT,276/1452926,4123653835,ERROR,XX001,"invalid page in block
>> 185809 of relation base/16477/7324724",,
>
> Probably not much we can do with this amount of info ... but I wonder if
> you identified which relation that was (table? index?)
It was actually a toast table.
From | Date | Subject | |
---|---|---|---|
Next Message | Léonard Benedetti | 2016-02-17 21:07:41 | Re: BUG #13440: unaccent does not remove all diacritics |
Previous Message | David G. Johnston | 2016-02-17 17:22:28 | Re: BUG #13967: Documentation. Plpgsql 'execute' description |