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:13:46
Message-ID: 49607DCA.2000908@paradise.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

regards

Mark

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Kirkwood 2009-01-04 09:18:30 Re: Latest version of Hot Standby patch: unexpected error querying standby
Previous Message Simon Riggs 2009-01-04 09:11:11 Re: Latest version of Hot Standby patch: unexpected error querying standby