Re: Resolving pg_standby -l
От | Simon Riggs |
---|---|
Тема | Re: Resolving pg_standby -l |
Дата | |
Msg-id | 1245942854.4038.115.camel@ebony.2ndQuadrant обсуждение исходный текст |
Ответ на | Re: Resolving pg_standby -l (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Resolving pg_standby -l
|
Список | 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
Вложения
В списке pgsql-hackers по дате отправления: