Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eV8uM-0006ul-9L for pgsql-performance@arkaria.postgresql.org; Sat, 30 Dec 2017 04:38:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eV8uL-00078p-7S for pgsql-performance@arkaria.postgresql.org; Sat, 30 Dec 2017 04:38:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eV8uK-00078g-MN for pgsql-performance@lists.postgresql.org; Sat, 30 Dec 2017 04:38:05 +0000 Received: from cp1.c0.inoc.net ([64.246.141.1]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eV8uG-00053P-AS for pgsql-performance@lists.postgresql.org; Sat, 30 Dec 2017 04:38:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=inoc.net; s=default; h=To:Date:Message-Id:Subject:Mime-Version: Content-Transfer-Encoding:Content-Type:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=0mRyRc7zdcZCfgDtEiJOGDI/gQG2YAvT0rVnKJbdvzA=; b=bDwBHb4Bc1yW7ycyirMCCdAxEm KNT3TrPwnKNfKNnhDRkGgEMQ3ZhPZ1uPZkuur5xjq4ySimnm+0v5qzh/jtI3Ydjvvut6FcsksX26X oIdbPf6O/sAOpS8Js0rnQCTvtVkLYnRuwp4oK/LSVYZs6WupGYizM9xumdcihfmJdcojHvD/JPkKH POXKP4u++6pk1kIUeuBfIUXLE2GC93agjwLNqkGu+fwcJFJ8DmDGnUGxSVmUVm6LOoMmBTQMPZxjR sHGZgBF+1P6lTX520mODbMV/jbrzTZlDZztlfDLCCr39bSN9NvV1KUVw2aUukPJkUqUgaEZKzn48I MMXZKt9g==; Received: from pool-108-4-157-162.albyny.fios.verizon.net ([108.4.157.162]:54119 helo=[10.99.3.101]) by cp1.c0.inoc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1eV8uD-0002iZ-K6 for pgsql-performance@lists.postgresql.org; Sat, 30 Dec 2017 04:37:57 +0000 From: Robert Blayzor Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: partitioning an existing table Message-Id: Date: Fri, 29 Dec 2017 23:37:56 -0500 To: pgsql-performance@lists.postgresql.org X-Mailer: Apple Mail (2.3445.5.20) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp1.c0.inoc.net X-AntiAbuse: Original Domain - lists.postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - inoc.net X-Get-Message-Sender-Via: cp1.c0.inoc.net: authenticated_id: rblayzor@inoc.net X-Authenticated-Sender: cp1.c0.inoc.net: rblayzor@inoc.net X-Source: X-Source-Args: X-Source-Dir: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk The docs claim that the master table =E2=80=9Cshould=E2=80=9D be empty. = It it possible to just create child tables off an existing master table = with data, then just inserting data into the new child tables. THe plan would be to keep data in the master table and purge it over = time until it=E2=80=99s eventually empty, then drop the indexes as well. Fully understanding that data needs to be placed in the right child = tables. Data outside of those child ranges would remain as =E2=80=9Cold = data=E2=80=9D in the master table. Just trying to grab if that=E2=80=99s an acceptable migration of live = data from a single large table and move into partitioning. Think of it = as a very large table of cyclic data that ages out. New data in child = tables while removing data from the master table over time. -- inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP: https://inoc.net/~rblayzor/