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

From Tom Lane
Subject Re: Resolving pg_standby -l
Date
Msg-id 19774.1245937896@sss.pgh.pa.us
Whole thread Raw
In response to Resolving pg_standby -l  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Resolving pg_standby -l  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
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_USEDcode to be disabled
#endif
        regards, tom lane


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Why does pg_standby require libpq.so.5?
Next
From: Tom Lane
Date:
Subject: Re: Extensions User Design