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

Re: Latest version of Hot Standby patch

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
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
Date: 2009-01-02 10:02:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Simon Riggs a écrit :
> On Wed, 2008-12-17 at 15:21 +0000, Simon Riggs wrote:
>> now contains a link to latest version of this patch. 
> v6 of Hot Standby now uploaded to Wiki (link above), with these changes:
> * Must ignore_killed_tuples and never kill_prior_tuple during index
> scans in recovery (v6)
>   * XLOG_BTREE_DELETE records handled correctly (v6)
>   * btree VACUUM code - must scan every block of index (v6)
>   * BEGIN TRANSACTION READ WRITE should throw error (v6)
> New test cycle starting with this patch over next few days.

I use latest CVS version. I tried to apply the patches and I have the
following error :

./ line 4: hs.prevent.v5.patch

I think you forgot to update the script. hs.prevent.v5.patch doesn't
exist in the tar file but hs.prevent.v6.patch does. Not sure we really
need this new file because I have a compilation error if I use the new
one. I don't have this error when I don't use the hs.prevent.v6.patch
file. Compilation error is :

utility.c: In function ‘ProcessUtility’:

utility.c:292: erreur: expected ‘)’ before ‘{’ token

utility.c:306: erreur: expected expression before ‘}’ token

And one file didn't want to get patched :

patching file src/include/catalog/pg_proc.h
Hunk #1 FAILED at 3223.
1 out of 1 hunk FAILED -- saving rejects to file

Not sure why. I did patch it manually, but I still have my compilation



In response to


pgsql-hackers by date

Next:From: Greg SmithDate: 2009-01-02 10:08:13
Subject: Re: posix_fadvise v22
Previous:From: Magnus HaganderDate: 2009-01-02 09:52:13
Subject: Re: Kerberos options requiring restart

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