Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dDAy2-0005Zb-Co for pgadmin-hackers@arkaria.postgresql.org; Tue, 23 May 2017 14:39:22 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dDAy1-0004DU-Vb for pgadmin-hackers@arkaria.postgresql.org; Tue, 23 May 2017 14:39:22 +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 1dDAxm-0003OS-Va for pgadmin-hackers@postgresql.org; Tue, 23 May 2017 14:39:07 +0000 Received: from mail-ua0-x234.google.com ([2607:f8b0:400c:c08::234]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dDAxj-0007z1-AG for pgadmin-hackers@postgresql.org; Tue, 23 May 2017 14:39:06 +0000 Received: by mail-ua0-x234.google.com with SMTP id j17so79091478uag.3 for ; Tue, 23 May 2017 07:39:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pivotal-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=a5MhFbsOGBdB9B0Mw/fGHljmR1UHo4/vTEM8+2JHlOQ=; b=FGAWuyaj5nfByLjRDfZCzVHdHwahL2ZNjW2pZ+6zJsygrEZWOEnWkivszRYGgzZazB AcawB6zo9cq7EvUD8/LJhTUfuE5iPhzdJLJI594yn9f38EF0IKAyzPzkVJt9ty+nQAED +IOEZPZ9dPvBSr09/4hsFnu1tCY4fp4j8xhhW3pDWcQJr/RSkR0Cdi1adDspsqPVR2Ak o8rsXe9/HNX6yhUeoFHJDxhPDCOwGa2isiaHbrCcIGozRmQnmgY8Ak+zmCL6yb9Txnuf jvWCn7SRKu1za1XlHfi2KvKEaC8fFcfCLV6d/OU68xJ/1jJbEKak4hEuPltN5cQ9jiH0 caJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=a5MhFbsOGBdB9B0Mw/fGHljmR1UHo4/vTEM8+2JHlOQ=; b=LOWsaZkGV4ERuvcK7Iv0RwFXSyhDRpY1hj2JHsmrGcmfOnAAE3F0h3Sv2XggkKTmZ6 b2dDLutJAUMzmRkuoxIDOecJwADSVSacEO8Hswtpk0mdiJWB2A6vjL4ZO6mPgnvVqq7P DnrTVTj3+MhZkYnnXP0dT8bNa/WGY7XUTKuW5CN4RQuyeuI9MMf+aDDAtR0+ebbEpIML 52iolXqFwdegPtLDF6sKPnLf3sovdXRu7g+OwJTifIiWVv+d+pGMxgWUQPV5VPe12O6l tKPxVZCXPKZqmfRRpuVBlaQ62i861KeQ6CyzNYYEyr+hiJY05DlQLgJr4uB/ZHIP1MJa ggMQ== X-Gm-Message-State: AODbwcCFwQttT7v/BeMpqf+qTqpXI9KJipslp4KI3js5U8ioiKGQiuEZ BLvZ18jYpElIq9mobCTQU/fYtfEDRZFq X-Received: by 10.159.55.161 with SMTP id q30mr12931399uaq.70.1495550340687; Tue, 23 May 2017 07:39:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.0.243 with HTTP; Tue, 23 May 2017 07:39:00 -0700 (PDT) In-Reply-To: References: From: Robert Eckhardt Date: Tue, 23 May 2017 10:39:00 -0400 Message-ID: Subject: Re: Declarative partitioning in pgAdmin4 To: Shirley Wang Cc: Akshay Joshi , pgadmin-hackers Content-Type: multipart/alternative; boundary="94eb2c040da8cd0317055031f2a2" X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --94eb2c040da8cd0317055031f2a2 Content-Type: text/plain; charset="UTF-8" On Tue, May 23, 2017 at 10:09 AM, Shirley Wang wrote: > > It's possible to design for the range and list partitions and know we can > achieve success because we understand how users would go through this > workflow. Not sure about expressions. > Maybe to pile on this a bit. When Shirley and I were discussing the workflows it was obvious when we were looking at 'normal' range or list partition use cases. Generally the only open question we had about the workflow was whether or not users would be building tables net new or whether they were more likely to have a table that was growing too large and therefore needed to create a new partitioned table. We couldn't think of a reason why a user would want to take the average of two columns and partition by this derived value. It added to the question of why/how a user would consider this as an idea a priori or whether this would be an insight given analysis of existing data. I assume this was supported for a specific use case. if you could share that it would be awesome. I guess the long and short of it is, we are having a difficult time imagining the workflow for this feature. -- Rob --94eb2c040da8cd0317055031f2a2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, May 23, 2017 at 10:09 AM, Shirley Wang <swang@pivotal.io>= ; wrote:

It's possible to design for the range and list pa= rtitions and know we can achieve success because we understand how users wo= uld go through this workflow. Not sure about expressions.
=

Maybe to pile on this a bit.=C2=A0

When Shirley and I were discussing the workflows it= was obvious when we were looking at 'normal' range or list partiti= on use cases. Generally the only open question we had about the workflow wa= s whether or not users would be building tables net new or whether they wer= e more likely to have a table that was growing too large and therefore need= ed to create a new partitioned table.=C2=A0

We cou= ldn't think of a reason why a user would want to take the average of tw= o columns and partition by this derived value. It added to the question of = why/how a user would consider this as an idea a priori or whether this woul= d be an insight given analysis of existing data.=C2=A0

=
I assume this was supported for a specific use case. if you could shar= e that it would be awesome. I guess the long and short of it is, we are hav= ing a difficult time imagining the workflow for this feature.
-- Rob
=C2=A0

--94eb2c040da8cd0317055031f2a2--