On Thu, Mar 22, 2012 at 11:06 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> We can use
> pg_xlogfile_name function to calculate that, but it cannot be executed in
> the standby. Another problem is that pg_xlogfile_name always uses
> current timeline for the calculation, so if the reported timeline is not
> the same as current one, pg_xlogfile_name cannot return the correct WAL
> file name. Making pg_controldata report that WAL file name gets rid of
> such a complexity.
i would think that pg_xlogfile_name() is not allowed in the standby
because ThisTimelineId is not very well defined in recovery but if you
extend pg_xlogfile_name() to also receive a timelineid as you
suggested in  then that version of the function could be allowed in
or there is something else i'm missing?
is that enough for you to solve your problem?
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2012-03-23 08:52:40|
|Subject: Re: Standbys, txid_current_snapshot, wraparound|
|Previous:||From: Fujii Masao||Date: 2012-03-23 04:06:48|
|Subject: Reporting WAL file containing checkpoint's REDO record in