On 06/30/2015 02:18 AM, Jeff Janes wrote:
On Mon, Jun 29, 2015 at 2:08 PM, Heikki Linnakangas wrote:
I just pushed a fix for this, but unfortunately it didn't make it
9.5alpha1.
Thanks. I think that that fixed it. It survived for over an hour this
time.
Thanks. I grepped through all the
On Mon, Jun 29, 2015 at 2:08 PM, Heikki Linnakangas wrote:
>
> Now kill -9 postmaster, and restart. Voila, the page headers are all zeros:
>
> postgres=# select * from page_header(get_raw_page('i_foo', 0));
> lsn| checksum | flags | lower | upper | special | pagesize |
> version |
> prun
On 06/29/2015 07:20 PM, Jeff Janes wrote:
On Mon, Jun 29, 2015 at 1:37 AM, Heikki Linnakangas wrote:
Another piece of info here that might be relevant. Almost all
UPDATE_META_PAGE xlog records other than the last one have two backup
blocks. The last UPDATE_META_PAGE record only has one backup
On 06/29/2015 01:12 AM, Jeff Janes wrote:
Now I'm getting a different error, with or without checksums.
ERROR: invalid page in block 0 of relation base/16384/16420
CONTEXT: automatic vacuum of table "jjanes.public.foo"
16420 is the gin index. I can't even get the page with pageinspect:
jjan
On Sun, Jun 28, 2015 at 12:31 PM, Heikki Linnakangas
wrote:
> On 06/26/2015 10:53 PM, Jeff Janes wrote:
>
>> On Fri, Jun 26, 2015 at 11:40 AM, Heikki Linnakangas
>> wrote:
>>
>> The page is being split (that's evident from "info=48" above).
>>> ginPlaceToPage calls GinNewBuffer, which calls Get
On 06/26/2015 10:53 PM, Jeff Janes wrote:
On Fri, Jun 26, 2015 at 11:40 AM, Heikki Linnakangas
wrote:
The page is being split (that's evident from "info=48" above).
ginPlaceToPage calls GinNewBuffer, which calls GetFreeIndexPage(). That
finds a page that can be recycled, and marks it as used.
On Fri, Jun 26, 2015 at 11:40 AM, Heikki Linnakangas
wrote:
> On 06/26/2015 08:02 PM, Jeff Janes wrote:
>
>> Under high load against f7bb7f0625771bc71869cda, I occasionally get:
>>
>> PANIC: XLogBeginInsert was not called
>>
>> It seems to only come from vacuuming.
>>
>> Here is an example back-
On 06/26/2015 08:02 PM, Jeff Janes wrote:
Under high load against f7bb7f0625771bc71869cda, I occasionally get:
PANIC: XLogBeginInsert was not called
It seems to only come from vacuuming.
Here is an example back-trace:
#0 0x003dcb632625 in raise () from /lib64/libc.so.6
#1 0x003dcb6
Under high load against f7bb7f0625771bc71869cda, I occasionally get:
PANIC: XLogBeginInsert was not called
It seems to only come from vacuuming.
Here is an example back-trace:
#0 0x003dcb632625 in raise () from /lib64/libc.so.6
#1 0x003dcb633e05 in abort () from /lib64/libc.so.6
#2
