| From: | Florian Pflug <fgp(at)phlo(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Linas Virbalas <linas(dot)virbalas(at)continuent(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot Backup with rsync fails at pg_clog if under load |
| Date: | 2011-09-23 16:49:18 |
| Message-ID: | 9C1909AF-D319-49BF-B3DA-5C3C30B5C849@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sep23, 2011, at 18:45 , Robert Haas wrote:
> Ah. I think you are right - Heikki made the same point. Maybe some
> of the stuff that happens just after this comment:
>
> /*
> * Initialize for Hot Standby, if enabled. We won't let backends in
> * yet, not until we've reached the min recovery point specified in
> * control file and we've established a recovery snapshot from a
> * running-xacts WAL record.
> */
>
>
> ...actually needs to be postponed until after we've reached consistency?
I came the the same conclusion. It seems the before we've reached consistency,
we shouldn't attempt to read anything because the data can be pretty arbitrarily
garbled.
best regards,
Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2011-09-23 16:51:29 | Re: unite recovery.conf and postgresql.conf |
| Previous Message | Florian Pflug | 2011-09-23 16:47:08 | Re: Hot Backup with rsync fails at pg_clog if under load |