Skip site navigation (1) Skip section navigation (2)

Re: Latest version of Hot Standby patch: unexpected error querying standby

From: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Latest version of Hot Standby patch: unexpected error querying standby
Date: 2009-01-04 09:18:30
Message-ID: 49607EE6.8020706@paradise.net.nz (view raw or flat)
Thread:
Lists: pgsql-hackers
Mark Kirkwood wrote:
> Simon Riggs wrote:
>> On Sun, 2009-01-04 at 21:03 +1300, Mark Kirkwood wrote:
>>
>>  
>>> bench=# \d history
>>>               Table "public.history"
>>>  Column |            Type             | Modifiers
>>> --------+-----------------------------+-----------
>>>  tid    | integer                     |
>>>  bid    | integer                     |
>>>  aid    | integer                     |
>>>  delta  | integer                     |
>>>  mtime  | timestamp without time zone |
>>>  filler | character(22)               |
>>>
>>> bench=# select now(),count(*) from history;
>>> ERROR:  could not open relation base/16384/16394: No such file or
>>> directory
>>>     
>>
>> >From my recreating your test case, the oids are consistent with the
>> History table. So the cache looks good.
>>
>> md.c should be cacheing the file descriptor so the second use of the
>> file should not be reopening it. I've not touched smgr/md so a missing
>> file error is a surprise.
>>
>> I wonder if this is an error associated with large file handling and
>> file forks? Smells like an FSM or VM error.
>>
>> Is the file actually missing? i.e. ls -l mydatadir/base/16384/16394*
>>
>>   
> Yeah -
> $ ls -l $PGDATA/base/16384/16394*
> ls: /data0/pgslave/8.4/base/16384/16394*: No such file or directory
>

This might be useful:

the other tables in the dataset (accounts, branches, tellers)  all 
behave as expected:

 bench=# select now(),count(*) from branches;
              now              | count
-------------------------------+-------
 2009-01-04 22:17:00.298597+13 |   100
(1 row)

I'm guessing something tied up with the fact that history has no rows to 
start with...

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2009-01-04 09:21:50
Subject: Re: Latest version of Hot Standby patch:unexpected error querying standby
Previous:From: Mark KirkwoodDate: 2009-01-04 09:13:46
Subject: Re: Latest version of Hot Standby patch: unexpected error querying standby

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group