Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tPklo-00F2JV-6i for pgsql-general@arkaria.postgresql.org; Mon, 23 Dec 2024 15:55:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tPkko-00C10R-LY for pgsql-general@arkaria.postgresql.org; Mon, 23 Dec 2024 15:53:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tPkko-00C10J-8L for pgsql-general@lists.postgresql.org; Mon, 23 Dec 2024 15:53:58 +0000 Received: from mail-oo1-xc34.google.com ([2607:f8b0:4864:20::c34]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tPkkm-000CYQ-1w for pgsql-general@lists.postgresql.org; Mon, 23 Dec 2024 15:53:57 +0000 Received: by mail-oo1-xc34.google.com with SMTP id 006d021491bc7-5f31f8f4062so1919240eaf.3 for ; Mon, 23 Dec 2024 07:53:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734969236; x=1735574036; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=lba2CnL/VVqA6vYww+FuCdyU7OurgTQqJeOz7ovnL7U=; b=MJgiJzm5q8jmWxrgVqb5TgVFFOap70QcKhhIOjQ+4qecApD9pd6+mXBD7+WFlLpN48 qObH1TiWWVFaI1rUEk110FAYmtv1K1lgVIB1Dujz7v/GOW9bzyQs5XzZOU7FIUUVWTdn XyawfULiNPFJFY2UcqABxnlwWticc+KE9IQL4I8pmXZu3S73RsCY2wqST8IW1LNSlTTL 2Rqty6FMXHtXYje6lV4BCA5pEaKvBpyPnIBy7jePJsP61IMnpk4qLen2z1IQ3elwQwST 1WUJ0oAxT2HU1dMRBGrrl9YLoe+xFA14PZSLllfi4hqUckStaCDCDcvmdnFJhEvsFhkH jkzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734969236; x=1735574036; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=lba2CnL/VVqA6vYww+FuCdyU7OurgTQqJeOz7ovnL7U=; b=F8vwo8PMWO9Q+0tgPrI+FqhFcAZE3ood0hF0IrqeLUgMwImcLOyO7Y4Mstl6HTUa1Q 2pSChnQ9XgDBXLZzUvRNhcB+fZo+dkF/E2BMtB8dDsTpY8vwk06tI8jE5Djm9o8FBgVF 1PMg3XgzuZ8TRTUFv/3GyhbHpHbysr8stAoquEgNrfJsfqmeuZsDewSzM4xcOIaHTzgg 25t/V/xFybkcadZVqKigNNo25hPEUV3Z5Sf9iHoDn5BpPQU/sFyg1woDycdzbGu62CGB QDUyXzY3NLHDicwTCQiXCxKckjTKs1zf31ldaQr+3n2MFal+p+GTDWQm8d2Vjjv6LD4r RUZQ== X-Gm-Message-State: AOJu0YykRYejRdwg1Y7xB+46rp1evc8O6gwYSAOrRRudrbKRVVFycu5L 8eq3c4AtLrZDYdax1qIK3Urd9h0NslCp7oToJpc4j0jsFTEqk6J+Cs+7oVitXCLBZ4kC51EySg6 K/BhW5GgH27AtGbvnpubpOBmxU9QJgrOq X-Gm-Gg: ASbGncuI4ORpschZEtuA/E+B3O6mvpDrI6y5fmCMee4lEDe++DK4busIL3HiN3YVhrI yTE7No87HvYO35aq+iH6ZtoIy8OJeCUfnyBJr9QAUOUJ67pwRLbvReutA6SLz/8XyYP3bm5Mj X-Google-Smtp-Source: AGHT+IHplPefpo51qS/6QVUVXf4o7Qb6JPQagq5VNp1Wy7borrQymgHLcLVVkIE81CzhMWn65l6AmYZjG5pEyqYB7rI= X-Received: by 2002:a05:6820:16a4:b0:5f2:d98b:d95d with SMTP id 006d021491bc7-5f62e771acdmr7064112eaf.4.1734969235733; Mon, 23 Dec 2024 07:53:55 -0800 (PST) MIME-Version: 1.0 From: Divyansh Gupta JNsThMAudy Date: Mon, 23 Dec 2024 21:23:44 +0530 Message-ID: Subject: Need help in database design To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000fe03ca0629f2004d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000fe03ca0629f2004d Content-Type: text/plain; charset="UTF-8" Hii Community, I need to provide a support for some functionality for my application for that I need to store 50 key value pair set, so I am in a dilemma, weather I create 50 new columns of int2 data type each column will contain value of a specific key or should I go with JSONB data type with 50 key value pair, the table on which I am going to do that all contains 1 Billion rows of data and have 84 hash partitions, I have gone through multiple articles some of them mentioned it's a good approach to create 50 new columns and some states that creating one JSONB would be best that's why I need your help to move forward, also I am ready to make H-Store instead of JSONB if it provides better performance. Please help me to comes out from that dilemma. Regards, Divyansh Gupta, Database Administrator --000000000000fe03ca0629f2004d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hii Community,

I need to provide a support for some functionality for my application fo= r that I need to store 50 key value pair set, so I am in a dilemma, weather= I create 50 new columns of int2 data type each column will contain value o= f a specific key or should I go with JSONB data type with 50 key value pair= , the table on which I am going to do that all contains 1 Billion rows of d= ata and have 84 hash partitions, I have gone through multiple articles some= of them mentioned it's a good approach to create 50 new columns and so= me states that creating one JSONB would be best that's why I need your = help to move forward, also I am ready to make H-Store instead of JSONB if i= t provides better performance.
Please help me to com= es out from that dilemma.

Regards,
Divyansh Gupta,
Da= tabase Administrator
--000000000000fe03ca0629f2004d--