Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dR00K-0003Wr-FE for pgsql-performance@arkaria.postgresql.org; Fri, 30 Jun 2017 17:46:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dR00J-0003TW-Tj for pgsql-performance@arkaria.postgresql.org; Fri, 30 Jun 2017 17:46:51 +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 1dR00J-0003TE-9f for pgsql-performance@postgresql.org; Fri, 30 Jun 2017 17:46:51 +0000 Received: from mail-ua0-x232.google.com ([2607:f8b0:400c:c08::232]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dR00G-0001v6-AR for pgsql-performance@postgresql.org; Fri, 30 Jun 2017 17:46:50 +0000 Received: by mail-ua0-x232.google.com with SMTP id g40so79917782uaa.3 for ; Fri, 30 Jun 2017 10:46:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=a6k+Z95Hsruc/tX5Iv25H5Wsrm1wu7NHx4cN5xPeAT8=; b=NU7G+EfN8MpWX4/Sz6ie6g6lTtkfdZL1quzjS3tam/Im0WTTebjdK/Rj3G1JJkiwC0 TAeUg820vNR1peO/AGvnQMCqD8dhwpmRvOKz9sAHYHqNxLN7VOgkro3ptX5fiW8hL4Y3 nBJi5/7aP5y2UzkxSzEjoPhwmLErlQN94OF/spnT8Hwqogmdeb5DCB32xSbgevoetEdy N64ePD59iXUdP33NVD6bLvwBsheX6K4TjAWku3XU0LAAvQNijtJehY6T7FFt6oM/8W+3 CvyKvlDEwGD38MNmXgn0oFSM1aNsmNjdQl5KHPPhLrj9laHr2CGqshN+OwGVaU9noVit K2Rw== 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=a6k+Z95Hsruc/tX5Iv25H5Wsrm1wu7NHx4cN5xPeAT8=; b=R2g1aaUHX9/PUIzAlY/GJWmiOdFovZ0EUXe4W2rHE9jJWGQ0P2dwLE4g8oRu4lIHx9 4SQkJQ4Ysn2dsnj8IDr2QS7Jm23k89W8O2oxB2IchgVCxZfHJLNSbHNK9eKuw2KaN+mb 4fWssKz4lq+zX7kj76AIJaWHi6EZepaUDrGYLSSevN1FnwpCR7+N8zB1/RXq8aIWipm6 J/S736Q35OY0//Cgv/dnbTYJB+hH55+Zb07eVDrJ5E7uGwYasdP37WrmXCTBYqrRPQ9D efhc2ybX7K3R5ve3STA1PQwv01FsSuHdt5vsIYYcp1LTrPSZo4d7IAaC56immBUnSW8O aYJg== X-Gm-Message-State: AKS2vOw88PI1xg8tqlCB+TOksA0ESGUAAh20VKqnH0ZjMtyoy91vz1a2 bdwh5o6LVDGwp6DonSyzm9lb7/I7Dg== X-Received: by 10.176.65.41 with SMTP id j38mr3901466uad.112.1498844806299; Fri, 30 Jun 2017 10:46:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.39.198 with HTTP; Fri, 30 Jun 2017 10:46:45 -0700 (PDT) In-Reply-To: References: From: Jeff Janes Date: Fri, 30 Jun 2017 10:46:45 -0700 Message-ID: Subject: Re: To: Yevhenii Kurtov Cc: "pgsql-performance@postgresql.org" Content-Type: multipart/alternative; boundary="94eb2c12359240c4c40553310098" List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org --94eb2c12359240c4c40553310098 Content-Type: text/plain; charset="UTF-8" On Thu, Jun 29, 2017 at 12:11 PM, Yevhenii Kurtov wrote: > Hi Jeff, > > That is just a sample data, we are going live in Jun and I don't have > anything real so far. Right now it's 9.6 and it will be a latest stable > available release on the date that we go live. > You need to use your knowledge of the application to come up with some plausible sample data. What happens when something succeeds? Does it get deleted from the table, or does it get retained but with a certain value of the status column? If it is retained, what happens to the priority and times_failed fields? The performance of your queuing table will critically depend on that. If you need to keep it once it succeeds, you should probably do that by deleting it from the queuing table and inserting it into a history table. It is much easier to keep performance up with that kind of design. Cheers, Jeff --94eb2c12359240c4c40553310098 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On T= hu, Jun 29, 2017 at 12:11 PM, Yevhenii Kurtov <yevhenii.kurtov@gma= il.com> wrote:
Hi Jeff,

That is just a sample data, we are going l= ive in Jun and I don't have anything real so far. Right now it's 9.= 6 and it will be a latest stable available release on the date that we go l= ive.=C2=A0


You n= eed to use your knowledge of the application to come up with some plausible= sample data.

What happens when something succeeds= ?=C2=A0 Does it get deleted from the table, or does it get retained but wit= h a certain value of the status column?=C2=A0 If it is retained, what happe= ns to the priority and times_failed fields?

The pe= rformance of your queuing table will critically depend on that. =C2=A0

If you need to keep it once it succeeds, you should pr= obably do that by deleting it from the queuing table and inserting it into = a history table.=C2=A0 It is much easier to keep performance up with that k= ind of design.

Cheers,

Je= ff
--94eb2c12359240c4c40553310098--