Added to TODO:
* Add checks for fclose() failure
---
Gavin Sherry wrote:
> On Fri, 30 May 2003, Tom Lane wrote:
>
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Gavin Sherry wrote:
> > >> There are various pl
On Fri, 30 May 2003, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Gavin Sherry wrote:
> >> There are various places in the backend, such as FreeFile(), where the
> >> return value of fclose() is not tested.
>
> > We are not checking fclose, probably because fclose failures are
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Gavin Sherry wrote:
>> There are various places in the backend, such as FreeFile(), where the
>> return value of fclose() is not tested.
> We are not checking fclose, probably because fclose failures are quite
> rare. Should we be concerned?
Probably.
On Fri, 30 May 2003, Bruce Momjian wrote:
> Gavin Sherry wrote:
> > Hi all,
> >
> > There are various places in the backend, such as FreeFile(), where the
> > return value of fclose() is not tested. Whilst we would often notice any
> > problems with writing to data files due to testing on fsync()
Gavin Sherry wrote:
> Hi all,
>
> There are various places in the backend, such as FreeFile(), where the
> return value of fclose() is not tested. Whilst we would often notice any
> problems with writing to data files due to testing on fsync(), it could
> affect things like COPY ... TO, CreateOpts
