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 1sU7XW-000awa-AG for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 16:30:02 +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 1sU7XU-002vKk-DY for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 16:30:00 +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 1sU7XU-002vKc-2H for pgsql-general@lists.postgresql.org; Wed, 17 Jul 2024 16:30:00 +0000 Received: from mail-oa1-x2b.google.com ([2001:4860:4864:20::2b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sU7XR-0002yW-Sp for pgsql-general@lists.postgresql.org; Wed, 17 Jul 2024 16:29:59 +0000 Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-260e8c98cc2so137454fac.0 for ; Wed, 17 Jul 2024 09:29:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721233796; x=1721838596; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=DW8UMoOjz8CMIDNNRq1NgL4hTk72D38eNAD+AHm2xNU=; b=SgriuJx64ZKE7iK8mA8tcLgJXobpJmRte4Vlqi8SvfhtX8ecwbhQWFj8ff9TGjEZAB VJPa3yvgHjkVAh0NdKu4AK5DJQLctAsOkHeIATHvaN096ziBmJV59BSslYUH2yBM/J6g LFAZ+p63V6W36PotcdnHlWqM7gs8+bn8ims3NIj5I1CCtD8HZc/glYfBSusnDH6NYQp4 aOsznFkSyc2FF8DTsTKny+NCobXVQ3WnYtlyRcdg+GloTehUnQau81RjT4HetjWC+Fjc 3rEMAKOYKQF+ADP1gIDPVpz5Bn5iYUkBi6L/VZZcUHDVJYy7ReB9Htp1L40Cq/sm9gcw 28tA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721233796; x=1721838596; h=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=DW8UMoOjz8CMIDNNRq1NgL4hTk72D38eNAD+AHm2xNU=; b=X4GPLEDweWyYh0ytOWUV9/8avVDKbcMXsAfQrnpO5Hys22YmWMeNeUq/WxxzuwQyyg FPlsUC3uT9uZfU4wjJJWeCXfLifFBZCcMMrJZDOG2R8BZDAKGg0xRgMa+7eA5yMSyOmQ Y4kh4/bN1Xb1oLrBH6FuZ6z32X2VJgkG1GuCLQFCqCDXycEOPzTO2ID9XL6ZMcNlqFOb j4SsXdPU3YbzIGdlSyeNXXg9FyCOxjikEqpzrJF3JumsrIVOAHt2gVQi1q/FmPGqBZ84 u7jQZ0CBmYasZjSF1x+aX4+nRgQIAhgSBVglRob9nCH2rz73XAMOEPjXWaVihi+lsgoZ z/qA== X-Gm-Message-State: AOJu0Yy6zrG5esTiVCzULhBwIyLSyNMt8lo58EFH9VQoUvFkrhLNIi3W Xlvl9KZr2QdStxHIqx33fBLsVQcyO5rcrizt9Su0cu/YO365fHQnKDgdl2YSKhrHgwdfPi8IJcJ GcF4qNe1Z+MiieYQ0iYXbNBr2Spwv3k2j X-Google-Smtp-Source: AGHT+IFRZPJuEVRJoTlz0/vaVzue5OijVkpztvyoSuNIeMV1Xd/YSHZ7t7u6mazDYcGCN5aB+iC6M9MVMcK5mkrUcMg= X-Received: by 2002:a05:6870:4409:b0:25e:ded:4147 with SMTP id 586e51a60fabf-260d8ee2bb3mr2011869fac.0.1721233795834; Wed, 17 Jul 2024 09:29:55 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 17 Jul 2024 12:29:44 -0400 Message-ID: Subject: Re: Semantic cache capability for Postgresql db To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000f9eb31061d73f8b4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f9eb31061d73f8b4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable What does "python client will support the pgprewarm cache usage" mean? Read the pgprewarm docs. On Wed, Jul 17, 2024 at 11:10=E2=80=AFAM pradeep t wrote: > 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 >>> >> > > -- > Thanks and regards > Pradeep.T > --000000000000f9eb31061d73f8b4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
What does "python client will support=C2=A0the= =C2=A0pgprewarm cache usage" mean?

Read the p= gprewarm=C2=A0docs.

On Wed, Jul 17, 2024 at 11:10=E2=80=AFAM pradeep t <<= a href=3D"mailto:pradeeprajkvr@gmail.com">pradeeprajkvr@gmail.com> w= rote:
Thanks, I'll check it out.=C2=A0
Also is there any pyt= hon client for the connection to pgprewarm?
Is the existing Postg= resql python client will support=C2=A0the=C2=A0pgprewarm cache usage also?<= /div>

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

pgprewarm Extension is av= ailable for=C2=A0Postgres


<= br>

On Tue, Jul 16, 2024 at 7:05=E2=80=AFPM pradeep t <pradeeprajkvr@gmail.com> wrote:
Hi,

Shall I use the=C2=A0P= ostgresql=C2=A0database for a=C2=A0semantic cache=C2=A0like the Redis = semantic cache?
Are we currently supporting such usag= e?

--
Thanks = and regards
Pradeep.T


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