Simon Riggs [EMAIL PROTECTED] writes:
On Thu, 2008-09-25 at 18:28 -0400, Tom Lane wrote:
After reading this for awhile, I realized that there is a rather
fundamental problem with it: it switches into consistent recovery
mode as soon as it's read WAL beyond ControlFile-minRecoveryPoint.
In a
Simon Riggs [EMAIL PROTECTED] writes:
New version of Postgres patch, v5. Implements suggested changes.
Ready for review and apply.
Applied with some revisions. The method for passing back freefunc
didn't work, so I made it pass the whole VariableStatsData struct
instead; this might allow some
On Sun, 2008-09-28 at 14:02 -0400, Tom Lane wrote:
It does nothing AFAICS for the
problem that when restarting archive recovery from a restartpoint,
it's not clear when it is safe to start letting in backends. You need
to get past the highest LSN that has made it out to disk, and there is
Simon Riggs [EMAIL PROTECTED] writes:
It does nothing AFAICS for the
problem that when restarting archive recovery from a restartpoint,
it's not clear when it is safe to start letting in backends. You need
to get past the highest LSN that has made it out to disk, and there is
no good way to
Hello all,
Just wanted to let everyone know I have committed this patch to the
PgFoundry uint project.
I have also updated the commit-fest wiki with this status.
Thanks to everyone (especially Jaime) for the feedback and reviews.
- Ryan
--
Sent via pgsql-patches mailing list
