Re: BUG #5451: pg_restore doesn't close input .tar archive

From: Pavel Golub <pavel(at)microolap(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5451: pg_restore doesn't close input .tar archive
Date: 2010-05-10 14:06:25
Message-ID: 264055715.20100510170625@gf.microolap.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello, Tom.

You wrote:

TL> Pavel Golub <pavel(at)microolap(dot)com> writes:
>> TL> I'm not sure what distinction you're trying to draw. Do you want us to
>> TL> add a close() just before exit()? If so, what for?

>> First of all, for uniformity I guess. :) .backup files are closed
>> properly.

>> And secondly, I'm using these sources in my project and I
>> need input file to be closed. Of course, I can find the place
>> where to insert close() by myself, but I beleive that this must be done in the
>> official release.

TL> I don't think so. The pg_restore code is not written to be a library.
TL> (Some have proposed making it into one, but there's a lot of work needed
TL> to make that happen.) Even if it were designed as a library, I don't
TL> think it would be the library's job to close the input file --- what
TL> if the surrounding app passes it stdin, for instance?

But .backup files are closed properly. :) What the difference?

TL> regards, tom lane

--
With best wishes,
Pavel mailto:pavel(at)gf(dot)microolap(dot)com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bryan Henderson 2010-05-10 15:55:21 Re: bool: symbol name collision
Previous Message Peter Eisentraut 2010-05-10 13:09:08 Re: bool: symbol name collision