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 1tsgsG-004gXZ-9R for pgadmin-hackers@arkaria.postgresql.org; Thu, 13 Mar 2025 11:37:16 +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 1tsgsF-00BTy1-04 for pgadmin-hackers@arkaria.postgresql.org; Thu, 13 Mar 2025 11:37:15 +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 1tsgqp-00BRZ9-8w for pgadmin-hackers@lists.postgresql.org; Thu, 13 Mar 2025 11:35:47 +0000 Received: from mail-yb1-xb2d.google.com ([2607:f8b0:4864:20::b2d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tsgqm-002bZB-38 for pgadmin-hackers@postgresql.org; Thu, 13 Mar 2025 11:35:46 +0000 Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-e6343c68b8fso666383276.2 for ; Thu, 13 Mar 2025 04:35:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1741865744; x=1742470544; 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=X7PwZRGKGqsoia3ZWaN7DY4kB8T0pyu1bKOJxopRXfM=; b=e4U4trVXay01KblgG2ND9T+ukR2v7sCnciTsovrq31Y+Zz1JaWBjaSEWge5O2R0mZy rtCLlD+E45piOwxlM3YofT0lM9XCxwfZAniFRbrLQDZU79lLSJZXhxlEDSELaN3isST6 YBjcm0WGaR2HERLzC8eJMHVpDHeMJo97Jnp/ubm4ffMSgQ466/YnRmSUezPRzVjNMGtz Z4uCZz+92Etj01qM2NsXORZDlbzW/W5nNX0PQCLwPZOfZB/UG5SEXRqDDRfZH5vJFtN/ aHzfjNA7Au4qYmHQ6YHDKbNz0zy21a6JHzVfs4gL+ca9rRqD5/u56rTEEgiIU3+PRHzN jnvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741865744; x=1742470544; 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=X7PwZRGKGqsoia3ZWaN7DY4kB8T0pyu1bKOJxopRXfM=; b=qL48yegkJBqSozGCVJxL+LjRlY7Ply5G0HF87Uyanwa7nZr+U82TDXjh3uP3W8CC+A 4Cch6s0PlM3v8wcxEyC4qC1XmkxdTz/xu8dl+lCtyjQ7hIbsuQ0oJXG5EIgRcDOQwWLj 0eVoAGh+OTjQXQmQc6kCvz/ZmA47yXla/QQg703LFOJ5uK9KulwGvNXGo1MP0hitl7Lf u8Sg1tuJn2L1sFcNhOhfadMl3orCd3kwMiXm0RDJs1MtOVkqw2OKPMn2+dNypuJZSQbW zNz6vqZx1O3M5R5ll4TsL61aKM0p2W5CvisJ98CR2Zyju5fY0u42m3g6P+j02rCBCYd6 aNpw== X-Gm-Message-State: AOJu0Yzv8y4WffLlbrBHFKt731tYxY54WQRxjfpowYpQeXJn0OuED9h0 OuTVVR7tHETE7VZpdlVnMNkBvjVQlq6DhV0LheqBd1N3+KOA1B1Paz298FEXeuNU3A+Jc5fnWWL CDmvyAJjpG2+Q+UDThbonAgqDPru1XE/tlui0HnR5BNvoPeBWpQ== X-Gm-Gg: ASbGncu3fxPXEYuge5XxmwA7s4NU4U7y2p+qwAWySO66QnCizr5kuauu8j1e9PtPKIQ jGWf8zmsquYrzOyeVFu5+EqpiGAmtMUTVwGih7ayZWfUJLsyW5CbvIQgLGwRMNHUpBUCZ7ITY0B uWAvPLSPWGpBRRFttgzFPc8T4nnK901QS5BZp3qasmDr+9puVvbD3ifFdfSKo= X-Google-Smtp-Source: AGHT+IFbLxwJMV3uU+FJLX99YTcK9OYkgiLCP89pe9WlkL3D0YipyyLRdBHSNENiJUQszk8VIT+msfXPSBo0FGzBfoo= X-Received: by 2002:a05:6902:2805:b0:e5d:929e:6311 with SMTP id 3f1490d57ef6-e635c1d8d40mr31856846276.36.1741865742648; Thu, 13 Mar 2025 04:35:42 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Yogesh Mahajan Date: Thu, 13 Mar 2025 17:05:05 +0530 X-Gm-Features: AQ5f1JpHTx-TtzRDUP9USkXmlYbO2XAWbaSMItXGnl5ns2f50VyfBL9tpQRyfpg Message-ID: Subject: Re: Regarding feature #3319 To: Dave Page Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000d66aef063037b887" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d66aef063037b887 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Dave, What about the query tools opened with an ad-hoc server, should we just open a query tool with data without connections? Thanks, Yogesh Mahajan EnterpriseDB On Thu, Mar 13, 2025 at 4:59=E2=80=AFPM Dave Page wrote= : > 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 wr= ote: >> >>> >>> >>> 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 pres= s > 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 >>> >>> > > -- > Dave Page > pgAdmin: https://www.pgadmin.org > PostgreSQL: https://www.postgresql.org > pgEdge: https://www.pgedge.com > > --000000000000d66aef063037b887 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Dave,

What about the query tools opened with an ad-hoc server, should=C2=A0we= just open a query tool with data without=C2=A0connections?

Thanks,
Yogesh Mahajan
EnterpriseDB


On Thu, Mar 13, 2025 at 4:59= =E2=80=AFPM Dave Page <dpage@pgadmi= n.org> wrote:
Hi
On T= hu, 13 Mar 2025 at 11:20, Yogesh Mahajan <yogesh.mahajan@enterprisedb.com&= gt; wrote:
Hi Dave,

<= div style=3D"font-family:verdana,sans-serif;font-size:small">Couple of foll= ow up questions -=C2=A0

Thanks,
Yogesh Mahajan
EnterpriseDB


On Thu, Mar 13, 2025 at 4:37=E2=80=AFPM Dave Page = <dpage@pgadmin.or= g> wrote:


On Tue, 11 Mar 2025 at 08:31, Yogesh Mahajan <yogesh.mahajan@enterprised= b.com> wrote:
He= llo Team,

C= ouple of more questions arose during discussion -=C2=A0

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

Yes :-). Ideally, as much of the original state as pos= sible should be restored.=C2=A0

So, sh= ould we open the psql without data and schema diff without comparison resul= ts?

I don't see= that we have any choice for psql. We absolutely should *not* attempt to au= tomatically re-run user queries.

For the schema di= ff, yes, that could be very expensive. The user can press the button if the= y want to incur that cost.
=C2=A0
Also for the query tools open with an ad-hoc se= rver, should=C2=A0we just open a query tool with data without=C2=A0connecti= ons?

=C2=A0
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 foll= ow the precedent there.
Curr= ently we are storing this data with json encoding done by the request=C2=A0= module.


--
Dave Page=
pgEdge: <= a href=3D"https://www.pgedge.com" target=3D"_blank">https://www.pgedge.com<= /a>



--
--000000000000d66aef063037b887--