From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: insert performance for win32 |
Date: | 2005-11-04 18:07:24 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3417DD7D5@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
> "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> > Nailed it.
>
> > problem is in mainloop.c -> setup_cancel_handler. Apparently you
can
> > have multiple handlers and windows keeps track of them all, even if
they
> > do the same thing. Keeping track of so many system handles would
> > naturally slow the whole process down.
>
> Yipes. So we really want to do that only once.
>
> AFAICS it is appropriate to move the sigsetjmp and
setup_cancel_handler
> calls in front of the per-line loop inside MainLoop --- can anyone see
> a reason not to?
hm. mainloop is re-entrant, right? That means each \i would reset the
handler...what is downside to keeping global flag?
> I'm inclined to treat this as an outright bug, not just a minor
certainly...
> performance issue, because it implies that a sufficiently long psql
> script would probably crash a Windows machine.
actually, it's worse than that, it's more of a dos on the whole system,
as windows will eventually stop granting handles, but there is a good
chance of side effects on other applications.
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | mark | 2005-11-04 18:10:03 | Re: Reducing the overhead of NUMERIC data |
Previous Message | Tom Lane | 2005-11-04 18:01:20 | Re: insert performance for win32 |
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2005-11-04 18:14:31 | Re: [PERFORM] insert performance for win32 |
Previous Message | Tom Lane | 2005-11-04 18:01:20 | Re: insert performance for win32 |