From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Randy Isbell <jisbell(at)cisco(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION |
Date: | 2009-01-16 02:42:23 |
Message-ID: | 233.1232073743@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-docs pgsql-hackers |
Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> Currently, stop wal filename is not always exclusive. If stop wal location
> doesn't indicate a boundary byte, its filename is inclusive. I'm afraid that
> the users cannot easily judge which "filename - 1" or "filename" should be
> waited. I mean that the users need to calculate whether stop wal location
> indicates a boundary byte or not before starting waiting. Such calculation
> should be done by the users?
No, which is why we provide functions to do it ;-)
It's really not worth changing the file contents. We're far more likely
to hear complaints like "you broke my archive script and I lost all my
data" than compliments about "the contents of this internal
implementation file are lots more sensible now".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2009-01-16 03:18:38 | Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION |
Previous Message | Fujii Masao | 2009-01-16 02:18:49 | Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION |
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2009-01-16 03:18:38 | Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION |
Previous Message | Fujii Masao | 2009-01-16 02:18:49 | Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2009-01-16 03:08:03 | Re: FWD: Re: Updated backslash consistency patch |
Previous Message | Fujii Masao | 2009-01-16 02:18:49 | Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION |