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 1tnKHn-004GcP-0S for pgsql-general@arkaria.postgresql.org; Wed, 26 Feb 2025 16:29:27 +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 1tnKHl-009C0x-MU for pgsql-general@arkaria.postgresql.org; Wed, 26 Feb 2025 16:29:25 +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 1tnKHl-009C0p-Ay for pgsql-general@lists.postgresql.org; Wed, 26 Feb 2025 16:29:25 +0000 Received: from fout-a3-smtp.messagingengine.com ([103.168.172.146]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tnKHi-000DUr-1I for pgsql-general@lists.postgresql.org; Wed, 26 Feb 2025 16:29:24 +0000 Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfout.phl.internal (Postfix) with ESMTP id E17501381124; Wed, 26 Feb 2025 11:29:22 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-09.internal (MEProxy); Wed, 26 Feb 2025 11:29:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1740587362; x=1740673762; bh=C8hIlhTloj68ebgx3duUfryG0GEbLs7Jw9RRbQ1bxt8=; b= d3ylwTX2pOLRXS/f2E719xSw/99l8RpkyOV/xXYVT3ObVWV8Jt7Ix0iYOwCd6Xcl FvvAGNVThGnq1mrQaBkaa7SmvOg+6aZ8YsbfHDriEoRar8RcS0HV1FoSCwZ/3gk9 cFOXpccUuVaMZmfgH3CTDKnLnTN8LkNxPf2o73GgS5VOKLza9PSEapVOBWW0zpcF T0PsJ8cA6EQcNnXkk+DbVgST+3uA+zU0+1RZA+mJPXhOZB/UxmLO83OY3UwshljS ceTjAIiWlDkqoZj74ptUZTWyEu7iVkyrIBrBEqcQBYLVck70mr2/HR08+6n3OmV8 udud6SS0I1HBpjW2N6a82g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1740587362; x=1740673762; bh=C 8hIlhTloj68ebgx3duUfryG0GEbLs7Jw9RRbQ1bxt8=; b=O1BpXijZmndi4p5S8 xMDCCFpMn6EcFKYCzUH8MgcZwxPWxp7NxGz3e18VrT+ZH4kcQUFs19AOqDOUu6o7 0UE9Jz4pSFNuJaCkKtw5yGP8VIZ7pWQR78LRw8MMlC10fG/Y20gu9R7J8jEASZ/b T/9HBqOE9n4qRmi0l8dndhlF7A4/kITNyNoSxzrLtNibd6bjiljm69mbUJDCZjUH kpHXMQly7NHl6UlyDXJVokvKOJip6kfP+XBQk6GOKikSwmKDvzqXcJvcEyXaSA2O uj5iw5MnFiM/3vI71dWJWtPkoZqHLCsQ5KmBqoR3V4lnUFvq4MrioRrsSDCi5fdW 2h3mg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgdekhedtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtvdej necuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrh esrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepiedvhfeiheehgeeuieel jeeitedtjeehudegfeelkedvleekhedtgfeiffefkedunecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghk lhgrvhgvrhdrtghomhdpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpd hrtghpthhtoheprgdrmhgrnhhtiihiohhssegtlhhouhgurdhgrghtvgifrgihnhgvthdr tghomhdprhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlsehlihhsthhsrdhpohhsth hgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 26 Feb 2025 11:29:21 -0500 (EST) Message-ID: Date: Wed, 26 Feb 2025 08:29:21 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Ideas about presenting data coming from sensors To: Achilleas Mantzios - cloud , pgsql-general@lists.postgresql.org References: <8d2dd92a-da16-435b-a38e-fe72191fc9d1@cloud.gatewaynet.com> <44a0b638-58f6-4a81-aadc-88aac3e2a842@cloud.gatewaynet.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2/26/25 01:27, Achilleas Mantzios - cloud wrote: > Hi Again > > Up to this day we have set the data acquisition system running for just > one ship and writing the code to display the data. For less than 20 days > we have 6M rows. > > I gave a shot to timescale, installed locally as an extension, it seems > much prettier than having to do all the partition mgmt by hand or other > tools. However this seems more than a complete engine with its own > workers, so this seems like something new and big which seems to me like > something to commit to for a long time, something to invest, on top of > the already 25+ commitment we have with PostgreSQL itself. > > So this is serious decision, so ppl please share your stories with > timescale . > I don't use timescale, so this will not be about specifics. It seems to me you are well on the way to answering your own question with the choices you presented: a) '... it seems much prettier than having to do all the partition mgmt by hand or other tools.' b) 'However this seems more than a complete engine with its own workers, ...' Either you do the work to build your own solution or you leverage off other folks work. The final answer to that comes down to what fits your situation. Which solution is easier to implement with the resources you have available. Either one is going to end up being a long term commitment. -- Adrian Klaver adrian.klaver@aklaver.com