On Mon, Feb 3, 2014 at 4:14 AM, Sawada Masahiko sawada.m...@gmail.comwrote:
On Sat, Feb 1, 2014 at 8:29 PM, Oskari Saarenmaa o...@ohmu.fi wrote:
31.01.2014 10:59, Sawada Masahiko kirjoitti:
I think the idea in the new progress_report() call (with force == true)
is
to make sure that
On Sat, Feb 1, 2014 at 8:29 PM, Oskari Saarenmaa o...@ohmu.fi wrote:
31.01.2014 10:59, Sawada Masahiko kirjoitti:
I think the idea in the new progress_report() call (with force == true) is
to make sure that there is at least one progress_report call that actually
writes the progress report.
31.01.2014 10:59, Sawada Masahiko kirjoitti:
On Tue, Jan 21, 2014 at 7:17 AM, Oskari Saarenmaa o...@ohmu.fi wrote:
18.11.2013 07:53, Sawada Masahiko kirjoitti:
On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress reporting that can grow to gigabytes
of
On Tue, Jan 21, 2014 at 7:17 AM, Oskari Saarenmaa o...@ohmu.fi wrote:
18.11.2013 07:53, Sawada Masahiko kirjoitti:
On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
I got error with
18.11.2013 07:53, Sawada Masahiko kirjoitti:
On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
I got error with following scenario.
$ initdb -D data -E UTF8 --no-locale
/* setting the
On Fri, Jan 10, 2014 at 3:56 AM, Mika Eloranta m...@ohmu.fi wrote:
On Thu, Jan 9, 2014, at 20:05, Magnus Hagander wrote:
On Thu, Nov 14, 2013 at 10:27 AM, Mika Eloranta m...@ohmu.fi wrote:
On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress
On Thu, Jan 9, 2014, at 20:05, Magnus Hagander wrote:
On Thu, Nov 14, 2013 at 10:27 AM, Mika Eloranta m...@ohmu.fi wrote:
On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
On Thu, Nov 14, 2013 at 10:27 AM, Mika Eloranta m...@ohmu.fi wrote:
On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
Same patch as an attachment.
Would it not make more sense to
On Thu, Jan 9, 2014, at 20:05, Magnus Hagander wrote:
On Thu, Nov 14, 2013 at 10:27 AM, Mika Eloranta m...@ohmu.fi wrote:
On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
On Thu, Nov 14, 2013 at 6:27 PM, Mika Eloranta m...@ohmu.fi wrote:
On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
Same patch as an attachment.
--
Mika Eloranta
Ohmu Ltd.
On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
Same patch as an attachment.
--
Mika Eloranta
Ohmu Ltd. http://www.ohmu.fi/
On 11/14/13 10:27 AM, Mika Eloranta wrote:
On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
Same patch as an attachment.
I can't comment on the usefulness of this patch, but the first
Iy
On Thu, Nov 14, 2013 at 3:51 AM, Mika Eloranta m...@ohmu.fi wrote:
Prevent excessive progress reporting that can grow to gigabytes
of output with large databases.
It might be interesting to add this patch to the next commit fest
where you could get a formal review:
13 matches
Mail list logo
