Re: Resolving pg_standby -l

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Resolving pg_standby -l
Date: 2009-06-25 13:51:36
Message-ID: 19774.1245937896@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndQuadrant(dot)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

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-06-25 14:16:18 Re: Extensions User Design
Previous Message Fujii Masao 2009-06-25 13:35:20 Re: Why does pg_standby require libpq.so.5?