"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Is there a reasonably cheap way to check whether the backend has a
> WAL file open and whether that one is the current append target?

Detecting whether we have a WAL file open is trivial (just look at
the static variable holding the file descriptor).  Determining whether
it's still the current append target is not so cheap though; it would
require examining shared-memory status which means taking a lock on
that status (and it's a high-traffic lock already).

We could have the open WAL file dropped if stale as a side-effect
anytime we have occasion to examine that shared state anyway.  But
in a nearly-read-only session such as your example I'm not sure that
would happen often enough to fix the problem.

			regards, tom lane

In response to

• Re: Deleted WAL files held open by backends in Linux at 2009-12-01 15:03:32 from Kevin Grittner

Responses

• Re: Deleted WAL files held open by backends in Linux at 2009-12-01 18:10:03 from Kevin Grittner

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2009-12-01 15:15:36
	Subject: Re: Block-level CRC checks
Previous:	From: Robert Haas	Date: 2009-12-01 15:09:49
	Subject: Re: [PATCH] Windows x64