| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Warm standby problems: Followup |
| Date: | 2009-10-27 20:20:43 |
| Message-ID: | 5457.1256674843@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"David F. Skoll" <dfs(at)roaringpenguin(dot)com> writes:
> Tom Lane wrote:
>> So, when it archives successfully the second time, which if either of
>> the two mismatched sha1's proves to have been correct?
> The one on the master server (lines wrapped for readability).
> However, the sha1 is taken after rsync exits, so it's unknown what
> the local sha1 actually was while the rsync was running.
Be worth taking the sha1 first to see if you get a different answer
about that, or maybe even doing it twice.
>> (I'm still wondering about the possibility that the WAL file is changing
>> underneath you ...)
> Well, can PostgreSQL change the WAL file while the archive_command is
> running?
It's not supposed to...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2009-10-28 01:37:03 | Re: [HACKERS] pg_standby doesnt't work |
| Previous Message | David F. Skoll | 2009-10-27 19:56:16 | Re: Warm standby problems: Followup |