X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0EF24D95BA for ; Fri, 4 Nov 2005 12:33:55 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 63831-06 for ; Fri, 4 Nov 2005 16:33:53 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 699C3D956C for ; Fri, 4 Nov 2005 12:33:52 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jA4GXqLg014317; Fri, 4 Nov 2005 11:33:52 -0500 (EST) To: "Merlin Moncure" Cc: pgsql-performance@postgresql.org Subject: Re: insert performance for win32 In-reply-to: <6EE64EF3AB31D5448D0007DD34EEB3417DD7CE@Herge.rcsinc.local> References: <6EE64EF3AB31D5448D0007DD34EEB3417DD7CE@Herge.rcsinc.local> Comments: In-reply-to "Merlin Moncure" message dated "Fri, 04 Nov 2005 11:16:45 -0500" Date: Fri, 04 Nov 2005 11:33:52 -0500 Message-ID: <14316.1131122032@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.006 required=5 tests=[AWL=0.006] X-Spam-Score: 0.006 X-Spam-Level: X-Archive-Number: 200511/83 X-Sequence-Number: 15340 "Merlin Moncure" writes: > ok, mingw gprof is claiming MainLoop is a culprit here, The only thing I can see that would be different for Windows is the SetConsoleCtrlHandler kernel call ... could that be expensive? Why do we have either sigsetjmp or setup_cancel_handler inside the per-line loop, rather than just before it? There is a lot of stuff in MainLoop that doesn't seem like it really needs to be done on every single line, particularly not the repeated fetching of psql variables that couldn't possibly change except inside HandleSlashCmds. But that all ought to be the same on Unix or Windows. regards, tom lane