Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ci3PS-0005bg-Aq for pgsql-hackers@arkaria.postgresql.org; Sun, 26 Feb 2017 18:19:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ci3PR-00045m-ST for pgsql-hackers@arkaria.postgresql.org; Sun, 26 Feb 2017 18:19:01 +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 1ci3PQ-00044K-A8 for pgsql-hackers@postgresql.org; Sun, 26 Feb 2017 18:19:00 +0000 Received: from mail-wm0-x229.google.com ([2a00:1450:400c:c09::229]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ci3PN-0005bK-5t for pgsql-hackers@postgresql.org; Sun, 26 Feb 2017 18:18:59 +0000 Received: by mail-wm0-x229.google.com with SMTP id v77so47437725wmv.0 for ; Sun, 26 Feb 2017 10:18:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=mWvpclKwqWZED79GxSKyZBsduoT415tboH0+wEEGtW0=; b=dtNvKMCcH4rVu6eKH+dcbV8oFtZLmjjue6vzZJp7dvOh2NXycfDJqLcnaVV+FS8wkO FiMQw22bq14U73ZRhlcM9iCdAmUR8svWgUZUVH9DfjCadAqyMnliLcOyMa/zoLuBbWTC wsb0JhGIoBwY1ra4h+ctLVMEA54aMTdNLlfy1gvsC4DyVr3Ewzr3/C7PiwLZT7gVz8Ut W3z+9OmQteY32N8+x9ZA1W1Rhz/g69+bWbVz4orz0k9VFXlizbbOsoTRkOWPUcWVW26S Uthp3QaM719stZMATKJ5g84afcwlvzDB08qOExEho5+eV2idXZRxfLXSEw8B2B381pEd pjbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=mWvpclKwqWZED79GxSKyZBsduoT415tboH0+wEEGtW0=; b=sI/0UlaDpKjIT78TvMQazAHa+Jx0I25isG18XM5UNYdo/zOX2xUDCV3jEeXpm3M9qw SMiMqrgEwmA6HLFbLmr46px7NOknKsyqIsUgqMcCvpsiL3yMkSszrf2vlIHHMv5FYyRL tEhVylLm929B1H0Yp31jhecCCEvVMz782Y7ipf5ASmK3HMRDYBD1ZrsW0gJb5+w+vHti 3jX0sVOIE/B8srfxOoWYMyrRVsqm+FLzIbcEPbwnFjUo9hmUJWG5kT0UUm+U2DQs3THm aIqwclN1mutgRVZgO734ZKDkmbmOMGm7MKiUATp9oaZAgQ4+f4qvdMVyL2bgUPvKB2ep yPZA== X-Gm-Message-State: AMke39nVpGK62EOoq3QXtq2ewA7aCyJnYDsvj+SE36HUFBRzo6GAhcT4d8pi14fiBv0SgT+qL+y2DQRB7d6SWtzVyu6FSwBkVF5ht31NF/5Qzy99ukDxFDGZrSUMt/Z6quO5i9kgQtxHUFlZjHcOfM9lYRSnYflTmhZ4gMlvwfk4kJFYBKTqs0kTVudnN46vBZkf331wZHid X-Received: by 10.28.197.77 with SMTP id v74mr11150159wmf.30.1488133135797; Sun, 26 Feb 2017 10:18:55 -0800 (PST) Received: from [192.168.0.105] (150.123.broadband11.iol.cz. [90.178.123.150]) by smtp.gmail.com with ESMTPSA id 4sm19104648wrp.61.2017.02.26.10.18.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Feb 2017 10:18:54 -0800 (PST) Subject: Re: Documentation improvements for partitioning To: Robert Haas , Simon Riggs References: <4ee94808-968a-57d7-c12a-a18f08138a2f@lab.ntt.co.jp> <20170220203320.GB2672@momjian.us> Cc: Bruce Momjian , Amit Langote , Corey Huinker , Pg Hackers From: Petr Jelinek Message-ID: Date: Sun, 26 Feb 2017 19:18:54 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.6 (--) 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 On 24/02/17 07:15, Robert Haas wrote: > On Fri, Feb 24, 2017 at 9:53 AM, Simon Riggs wrote: >> The good news is that logical replication DOES work with partitioning, >> but only for a Publication with PUBLISH INSERT, pushing from a normal >> table to a partitioned one. Which is useful enough for first release. >> >> The work on having UPDATE work between partitions can be used to make >> updates and deletes work in logical replication. That might yet be >> made to work in this release, and I think we should look into it, but >> I think it can be left til next release if we try. > > Are you speaking of the case where you want to replicate from an > unpartitioned table to a partitioned table? I would imagine that if > you are replicating between two identical partitioning hierarchies, it > would just work. (If not, that's probably a bug, though I don't know > whose bug.) > Yes same hierarchies will work but mainly because one has to add partitions themselves to publication currently. I guess that's the limitation we might have to live with in 10 as adding the whole partitioned table should probably work for different hierarchies when we enable it and I am not quite sure that's doable before start of the CF at this point. -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers