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 1tsgkH-004eU5-Dq for pgadmin-hackers@arkaria.postgresql.org; Thu, 13 Mar 2025 11:29:01 +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 1tsgkF-00BGxF-Qu for pgadmin-hackers@arkaria.postgresql.org; Thu, 13 Mar 2025 11:28:59 +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 1tsgkF-00BGx6-FT for pgadmin-hackers@lists.postgresql.org; Thu, 13 Mar 2025 11:28:59 +0000 Received: from mail-lf1-x12c.google.com ([2a00:1450:4864:20::12c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tsgkD-002bVf-1b for pgadmin-hackers@postgresql.org; Thu, 13 Mar 2025 11:28:58 +0000 Received: by mail-lf1-x12c.google.com with SMTP id 2adb3069b0e04-549963b5551so844897e87.2 for ; Thu, 13 Mar 2025 04:28:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1741865336; x=1742470136; darn=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=ch39To/o0r8teQWMr/OLDCgHyjau2N+TZP/1zP4WlHQ=; b=eAIVY7rTeDwKPXeR0wvlvvIZ3lybelyR6mY/bf14lDyi7nkBhV7FvUEqO59I/1IDMO oMu7T5+tXk1XYTaej8jx8Mh3GBzGZdgNRq2xCrRSpdsPoW90aJaAuZF4X/573eeL0A/W lHHHj+k3U2KJb/goQIaL+pGoJbMn2WKh4x4kSJ5Y9lgSSTBvZouS+CfOetmHN6I5PcWI xE7oQkyu6NN73695+sYw5JEtxbOyIY/LeHXbDH/N9CE6AJbIghXNtMg14RCpp4FexqkR KQynMFXy2i81Q7WM2fHzae9xwN2N14kY3CcG3HUnbGmOnEofJ2iGytbUKDCXjt6UWqr6 ZJPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741865336; x=1742470136; 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=ch39To/o0r8teQWMr/OLDCgHyjau2N+TZP/1zP4WlHQ=; b=SG4hNKEahmRTtjJXrG4ZuENwkjKk1TNXlMlVP8HSpufgJTNO7L9su8XY3nIcXF2AYC +mKx9w11/u11qIrlsTMj4/6k2hRY3OS55M4tgu0p8l5lEKUmekLBxRelqgpuqtePktki 3AZAMmBikon3aMbuNaDJ+RkepJSRTCZf24yq/Xm6h2ZC5H9R1x+aKsN9+NLc9J79g8Ar eyxWHW59GSnwYkbAuCbNS/oP53HCtwH58ZPIRqJZjwKQPSjUMs3DmcP0RA4Tji3o9vvG OqK5TiaXQvnmEiOwcQaC9xIIsBA533qeSZN883955syepnGjb1Nqk8ZwL0oCGb7ajH// CRzw== X-Gm-Message-State: AOJu0YwzosUP1xAr0aMIRdm3gRK+ptVUCQFzfJBcGWzcCzVPQ3rxc3/k M2tnvQQIx7BxLIvJzSf9sveYNTgM2zDs8L+HVh7WncOeYTdiZUM3r/xdpKvOeiJS6jkdlPHGb/E Ml5stFoKYU+vr98MgXrVb/qtFBMjqD+6QYrPCFa2WgnxUPb3pOQ== X-Gm-Gg: ASbGncvwmUEqX2k/nWU4wzxe/vfKfOXkVezN4CLJeD9QNIsfbx/v0aDA+px+huEWRRd zQLH+8A5BB7JJVNxvixH40xVhV1osEC1LuD6fk2wlx3IlCREuflHE+Uz4QhxjRrPc2HShwvQVJc Su8rMJvwIZaO2aHuSCeG3tOpFvJiXY X-Google-Smtp-Source: AGHT+IHWfjDwj26mKnm42vx6offh4ElCTv6e3zmF3ytlC3smSnCrN71D12DynTsDOU0jw2DSqIlv9RT3IlD5i0pgvlI= X-Received: by 2002:a05:6512:234d:b0:549:8c86:740d with SMTP id 2adb3069b0e04-549abac0101mr4497316e87.18.1741865336098; Thu, 13 Mar 2025 04:28:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Thu, 13 Mar 2025 11:28:45 +0000 X-Gm-Features: AQ5f1JoijNGhqJFsZ1fFw3PTDUiUg2JDRXGxOmRv_w9d9XeLb-7_2IjJEp_9hXQ Message-ID: Subject: Re: Regarding feature #3319 To: Yogesh Mahajan Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000009af00f063037a0a2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009af00f063037a0a2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi On Thu, 13 Mar 2025 at 11:20, Yogesh Mahajan < yogesh.mahajan@enterprisedb.com> wrote: > Hi Dave, > > Couple of follow up questions - > > Thanks, > Yogesh Mahajan > EnterpriseDB > > > On Thu, Mar 13, 2025 at 4:37=E2=80=AFPM Dave Page wro= te: > >> >> >> On Tue, 11 Mar 2025 at 08:31, Yogesh Mahajan < >> yogesh.mahajan@enterprisedb.com> wrote: >> >>> Hello Team, >>> >>> Couple of more questions arose during discussion - >>> >>> 1.What all tools should we reopen while restoration? It could be Query >>> tool, ERD, Psql, Schema diff as of now may get additional in future. >>> >> >> Yes :-). Ideally, as much of the original state as possible should be >> restored. >> > > So, should we open the psql without data and schema diff without > comparison results? > I don't see that we have any choice for psql. We absolutely should *not* attempt to automatically re-run user queries. For the schema diff, yes, that could be very expensive. The user can press the button if they want to incur that cost. > Also for the query tools open with an ad-hoc server, should we just open = a > query tool with data without connections? > > >> >>> 2.Can we use an existing crypt key to encrypt the query data or simply >>> json encoding should be enough? >>> >> >> We're already storing the query history, so we should follow the >> precedent there. >> > Currently we are storing this data with json encoding done by the > request module. > > >> -- >> Dave Page >> pgAdmin: https://www.pgadmin.org >> PostgreSQL: https://www.postgresql.org >> pgEdge: https://www.pgedge.com >> >> --=20 Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org pgEdge: https://www.pgedge.com --0000000000009af00f063037a0a2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

On Thu, 13 Mar 2025 at 11:20,= Yogesh Mahajan <yoge= sh.mahajan@enterprisedb.com> wrote:
Hi Dave,

Couple of follow up questions -=C2=A0

= Thanks,
Yogesh Mahajan
EnterpriseDB


On Thu, Mar 13, 20= 25 at 4:37=E2=80=AFPM Dave Page <dpage@pgadmin.org> wrote:
=


=
On Tue, 11 Mar 2025 at 08:31, Yogesh = Mahajan <yogesh.mahajan@enterprisedb.com> wrote:
Hello Team,

Couple of more questions arose during discus= sion -=C2=A0

1.What all tools should we reopen while restoration? It could be Query to= ol, ERD, Psql, Schema diff as of now may get additional=C2=A0in future.

Yes :-). Ideally, as m= uch of the original state as possible should be restored.=C2=A0
=

So, should we open the psql without data and sche= ma diff without comparison results?

I don't see that we have any choice for psql. We absol= utely should *not* attempt to automatically re-run user queries.
=
For the schema diff, yes, that could be very expensive. The = user can press the button if they want to incur that cost.
=C2=A0=
Also for the que= ry tools open with an ad-hoc server, should=C2=A0we just open a query tool = with data without=C2=A0connections?

=C2=A0
2.Can we use an existing crypt key to encr= ypt the query data or simply json encoding should be enough?

We're already storing the que= ry history, so we should follow the precedent there.
Currently we are storing this data with json encod= ing done by the request=C2=A0module.


--
<= /div>


--
--0000000000009af00f063037a0a2--