Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> We could stick a volatile on it but I'd like to find out why this
> >> particular variable seems to need that.
>
> > You ready for this; changing 'bool' to 'int' supressed the warning:
> > int fast = PG_GETARG_BOOL(1);
>
>
Bruce Momjian writes:
> Tom Lane wrote:
>> We could stick a volatile on it but I'd like to find out why this
>> particular variable seems to need that.
> You ready for this; changing 'bool' to 'int' supressed the warning:
> int fast = PG_GETARG_BOOL(1);
Well, that's a compiler bug :-(
Tom Lane wrote:
> Bruce Momjian writes:
> > Any idea why I am seeing this warning with the new pg_start_backup()
> > 'fast' flag?
>
> > xlog.c:6917: warning: variable `fast' might be clobbered by
> > `longjmp' or `vfork'
>
> > The line is in a PG_ENSURE_ERROR_CLEANUP() block. This is wi
Bruce Momjian writes:
> Any idea why I am seeing this warning with the new pg_start_backup()
> 'fast' flag?
> xlog.c:6917: warning: variable `fast' might be clobbered by
> `longjmp' or `vfork'
> The line is in a PG_ENSURE_ERROR_CLEANUP() block. This is with gcc
> version 2.95.3.
Th
Any idea why I am seeing this warning with the new pg_start_backup()
'fast' flag?
xlog.c:6917: warning: variable `fast' might be clobbered by
`longjmp' or `vfork'
The line is in a PG_ENSURE_ERROR_CLEANUP() block. This is with gcc
version 2.95.3.
--
Bruce Momjian http
