| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Hannu Krosing <hannu(at)skype(dot)net> |
| Subject: | Re: Forcing current WAL file to be archived |
| Date: | 2006-08-09 11:56:04 |
| Message-ID: | 1155124565.2368.95.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Sat, 2006-08-05 at 23:57 -0400, Tom Lane wrote:
> I also made the new user-level functions a bit
> more orthogonal, so that filenames could be extracted from the
> existing functions like pg_stop_backup.
Something Hannu wrote has just reminded me that
pg_current_xlog_location() returns the current Insert pointer rather
than the current Write pointer.
That would not be useful for streaming xlog records would it?
Methinks it should be the Write pointer all of the time, since I can't
think of a valid reason for wanting to know where the Insert pointer is
*before* we've written to the xlog file. Having it be the Insert pointer
could lead to some errors.
Any objections if I correct that?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mohan R | 2006-08-09 11:58:54 | unsubscribe |
| Previous Message | Simon Riggs | 2006-08-09 11:48:08 | Re: [HACKERS] Restartable Recovery |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2006-08-09 13:05:02 | Re: [HACKERS] [PATCHES] Values list-of-targetlists patch for comments (was Re: |
| Previous Message | Simon Riggs | 2006-08-09 11:48:08 | Re: [HACKERS] Restartable Recovery |