Re: Resolving pg_standby -l - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Resolving pg_standby -l
Date
Msg-id 1245942854.4038.115.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Resolving pg_standby -l  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Resolving pg_standby -l
List pgsql-hackers
On Thu, 2009-06-25 at 09:51 -0400, Tom Lane wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
> > --- 610,621 ----
> >                   }
> >                   break;
> >               case 'l':            /* Use link */
> > !                 /*
> > !                  * Link feature disabled, possibly permanently. Linking
> > !                  * causes a problem after recovery ends that is not currently
> > !                  * resolved by PostgreSQL. 25 Jun 2009
> > !                     restoreCommandType = RESTORE_COMMAND_LINK;
> > !                 */
> >                   break;
> >               case 'r':            /* Retries */
> >                   maxretries = atoi(optarg);
>
> Just for future reference: the above is going to look like hell after
> pgindent gets its hands on it.  Better style for this project is
>
>     /*
>      * ordinary comment block
>      */
> #ifdef NOT_USED
>     code to be disabled
> #endif

Will do, thanks. Patch to cleanup as advised is attached.

--
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Extensions User Design
Next
From: Michael Meskes
Date:
Subject: Re: ECPG dynamic cursor, SQLDA support