From: Simon Riggs <simon@2ndquadrant.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: David Fetter <david@fetter.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] insert performance for win32
Date: Sun, 06 Nov 2005 09:00:05 +0000
Message-ID: <1131267605.8300.2055.camel@localhost.localdomain> (raw)
In-Reply-To: <200511041821.jA4IL7117478@candle.pha.pa.us>
References: <200511041821.jA4IL7117478@candle.pha.pa.us>
On Fri, 2005-11-04 at 13:21 -0500, Bruce Momjian wrote:
> David Fetter wrote:
> > On Fri, Nov 04, 2005 at 01:01:20PM -0500, Tom Lane wrote:
> > > I'm inclined to treat this as an outright bug, not just a minor
> > > performance issue, because it implies that a sufficiently long psql
> > > script would probably crash a Windows machine.
> >
> > Ouch. In light of this, are we *sure* what we've got a is a candidate
> > for release?
>
> Good point. It is something we would fix in a minor release, so it
> doesn't seem worth doing another RC just for that.
Will this be documented in the release notes? If we put unimplemented
features in TODO, where do we list things we regard as bugs?
Best Regards, Simon Riggs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: simon@2ndquadrant.com, pgman@candle.pha.pa.us, david@fetter.org, tgl@sss.pgh.pa.us, merlin.moncure@rcsonline.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] insert performance for win32
In-Reply-To: <1131267605.8300.2055.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox