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 1sU6Hy-000R7H-MV for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 15:09:54 +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 1sU6Hw-001tRZ-TI for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 15:09:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sTkQd-0028az-8P for pgsql-general@lists.postgresql.org; Tue, 16 Jul 2024 15:49:23 +0000 Received: from mail-oi1-x230.google.com ([2607:f8b0:4864:20::230]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sTkQa-002R3v-Hd for pgsql-general@lists.postgresql.org; Tue, 16 Jul 2024 15:49:22 +0000 Received: by mail-oi1-x230.google.com with SMTP id 5614622812f47-3d9ddfbbc58so3386991b6e.2 for ; Tue, 16 Jul 2024 08:49:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721144958; x=1721749758; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qJYm/oq2ug3PiNcJW0amlqjQQFxjvC0Q9SF2+m+7UxY=; b=nDLJcisKtzLkELv2KDE73EpGdCoY99p9n9isPeMO0D7B8tBhSNWkjfDnLUSf6bSMUF e2FiM6PEjkWHRnwiZV0fNKsezZgA8Oc4QjW1XwiiVOpi8v9/r0gqQ9H6vaGNXQP+IxnR LuVVaUXwyPYL0kGgrnEJPijYFIY5NZ7BaiOW88rV0ivcCy7HeSzwWCjlZMVb3hgs+MnM 86bSIDWX9xFdWQJHhuOZi6AX409ss9OIHnMzKwqCOpEz3kFpwrVbals4joiy+s25ZuUR VWRHrFZ9VMq8v1MpkfhczY8wTNyQs9TvrcOLC/FpR1+jb1v3QUuitM+CUxwLjGwsj3gQ tLAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721144958; x=1721749758; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qJYm/oq2ug3PiNcJW0amlqjQQFxjvC0Q9SF2+m+7UxY=; b=v43V4Y+jrWIKJqltC1TiLa3gG0HxkPGVMO18Hogaq79d9bb1fwFlte6iL66EmIuqAG OKRuxiOEZqYw3sI8J3vv3LwT8XTPTodFObjOOEJb/2bAcW5bEOPGv+vzlqjRTEBHfakl fWLl34sMCGyWMENZYKRevwaO66kpFUg3n9QQusEOJuZbZ86XoOxx7OikUTBipOCInRnP DmhsR7peWurR2BGdE0glpd6H4tKhJgPKs8AOtqsgi7Ae9DElMMknZYpOEZSQZY7cltqE otYgvcSPaWJi5o1+NrU4vim3AtH7BcNfMiZBULkoRqP54EOHzy5d04EnEc0VSQc1rWGa datw== X-Gm-Message-State: AOJu0YxHXFfST41YOZaOi+Ak1R0HMhp83Alrk8aSOix5z7Bn3dPk4Thm 7ahIO986djOJyIXEyEDZn+YUd1k95w1XeeaVHh0aOSh/ztBbQOGWbDcNt6vVKx3iHlF7GXhbJ7y uOFt9vZldtWsjAh0LZh9HvsD8EMI= X-Google-Smtp-Source: AGHT+IFWsse8Dm1sdXorPZfQ8voSSbXrG6/GNJQY9qnUYgQpaQ9gv3M0lmK4ekj91wAcoXgxZknogGrzbU0QAviDzX0= X-Received: by 2002:a05:6808:1908:b0:3d5:1a20:e8d9 with SMTP id 5614622812f47-3dac7b967a9mr3143576b6e.24.1721144958398; Tue, 16 Jul 2024 08:49:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: pradeep t Date: Tue, 16 Jul 2024 21:19:07 +0530 Message-ID: Subject: Re: Semantic cache capability for Postgresql db To: Kashif Zeeshan Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000da4205061d5f499e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000da4205061d5f499e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks, I'll check it out. Also is there any python client for the connection to pgprewarm? Is the existing Postgresql python client will support the pgprewarm cache usage also? On Tue, Jul 16, 2024 at 9:01=E2=80=AFPM Kashif Zeeshan wrote: > Hi Pradeep > > pgprewarm Extension is available for Postgres > > https://www.postgresql.org/docs/current/pgprewarm.html > > > > On Tue, Jul 16, 2024 at 7:05=E2=80=AFPM pradeep t wrote: > >> Hi, >> >> Shall I use the Postgresql database for a* semantic cache *like the >> Redis semantic cache? >> Are we currently supporting such usage? >> >> -- >> Thanks and regards >> Pradeep.T >> > --=20 Thanks and regards Pradeep.T --000000000000da4205061d5f499e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, I'll check it out.=C2=A0
Also is there= any python client for the connection to pgprewarm?
Is the existi= ng Postgresql python client will support=C2=A0the=C2=A0pgprewarm cache usag= e also?

On Tue, Jul 16, 2024 at 9:01=E2=80=AFPM Kashif Zeeshan <kashi.zeeshan@gmail.com> wro= te:
Hi=C2=A0Pradeep

pgprewarm Extension is available fo= r=C2=A0Postgres



<= /div>
O= n Tue, Jul 16, 2024 at 7:05=E2=80=AFPM pradeep t <pradeeprajkvr@gmail.com> wrot= e:
Hi,

Shall I use the=C2=A0Postgresql<= span style=3D"color:rgb(31,35,40);font-family:-apple-system,BlinkMacSystemF= ont,"Segoe UI","Noto Sans",Helvetica,Arial,sans-serif,&= quot;Apple Color Emoji","Segoe UI Emoji";font-size:14px">=C2= =A0database for a=C2=A0semantic cache=C2=A0like the Redis semantic c= ache?
Are we currently supporting such usage?<= /div>

--
Thanks and regard= s
Pradeep.T


--
Thanks and regards
Pradeep.T
--000000000000da4205061d5f499e--