Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UulLl-0008TC-Fe for pgsql-hackers@arkaria.postgresql.org; Thu, 04 Jul 2013 15:21:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1UulLk-0004Dr-MI for pgsql-hackers@arkaria.postgresql.org; Thu, 04 Jul 2013 15:21:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UulLj-0004Dk-Gx for pgsql-hackers@postgresql.org; Thu, 04 Jul 2013 15:21:35 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UulLd-0006Um-1K for pgsql-hackers@postgresql.org; Thu, 04 Jul 2013 15:21:35 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id r64FL532021930; Thu, 4 Jul 2013 11:21:05 -0400 (EDT) From: Tom Lane To: Andres Freund cc: KONDO Mitsumasa , Robert Haas , Heikki Linnakangas , PostgreSQL-development Subject: Re: Improvement of checkpoint IO scheduler for stable transaction responses In-reply-to: <20130704130555.GA1403@awork2.anarazel.de> References: <51BEB6F5.7070907@lab.ntt.co.jp> <51C40EF4.1080201@lab.ntt.co.jp> <51C9D03B.10107@vmware.com> <51C9FD5C.5050706@vmware.com> <51CD873A.5070705@lab.ntt.co.jp> <51D3DE55.6030901@lab.ntt.co.jp> <51D56A5B.3050504@lab.ntt.co.jp> <20130704130555.GA1403@awork2.anarazel.de> Comments: In-reply-to Andres Freund message dated "Thu, 04 Jul 2013 15:05:55 +0200" Date: Thu, 04 Jul 2013 11:21:05 -0400 Message-ID: <21929.1372951265@sss.pgh.pa.us> X-Pg-Spam-Score: -2.1 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Andres Freund writes: > I don't like going in this direction at all: > 1) it breaks pg_upgrade. Which means many of the bigger users won't be > able to migrate to this and most packagers would carry the old > segsize around forever. > Even if we could get pg_upgrade to split files accordingly link mode > would still be broken. TBH, I think *any* rearrangement of the on-disk storage files is going to be rejected. It seems very unlikely to me that you could demonstrate a checkpoint performance improvement from that that occurs consistently across different platforms and filesystems. And as Andres points out, the pain associated with it is going to be bad enough that a very high bar will be set on whether you've proven the change is worthwhile. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers