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 1tsgwo-004hiB-6l for pgadmin-hackers@arkaria.postgresql.org; Thu, 13 Mar 2025 11:41:58 +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 1tsgwm-00BaN5-9y for pgadmin-hackers@arkaria.postgresql.org; Thu, 13 Mar 2025 11:41:56 +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 1tsgwl-00BaDU-P4 for pgadmin-hackers@lists.postgresql.org; Thu, 13 Mar 2025 11:41:56 +0000 Received: from mail-yb1-xb2f.google.com ([2607:f8b0:4864:20::b2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tsgwi-002bbj-1D for pgadmin-hackers@postgresql.org; Thu, 13 Mar 2025 11:41:54 +0000 Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-e60aef2711fso636393276.2 for ; Thu, 13 Mar 2025 04:41:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1741866112; x=1742470912; 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=O5lGSxaaKbZKN152OuCSerD3qXmT/HSxtn9nmgS+Wj8=; b=Wm+AboIjlDlgvj7oiXMviR9MJ6G1T8ULdWZzWIqNuEyAUs7y/eoWX7CBoQ4EXxeqnJ 3ttffkLSep/DC5/y6OxahvB9Hg8kqwFfbCVD6lznbA/rBVdTvfczxJ1mCwoV911WugED RsXHZMurH84sDDRjKUW+js+9RfO7zXEc9pjtZXvE9i+Uly3HyGpNpOp4ENFbkpSeFWD3 aFzxLStJ5/3Y8Aym1DdSD7x5boCb8ropZHrR86ZawERe8o8MqOWpHP4OBKGcNZw6An8M D0XFWn+26Y9HCuxaVQ4/oO9Sk8M0xD6YtQNN8LNWfqZ+k2RLH8QJRz8xr7uM2s39sGSP GM+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741866112; x=1742470912; 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=O5lGSxaaKbZKN152OuCSerD3qXmT/HSxtn9nmgS+Wj8=; b=aoMMWin3F3JgtfjNhXxuhIomkr3AGaEQDSvEul1qGY3Cpz7tZytQAR6bWEZxErAhQe x9LeZYUSsC3Kk/VDfgcjiqvTsSKDfAAqzoer4eZASfPU/yfzjgUR3PiTn1kbMGxUrD8K vDkbUMFDi+fcurZA0dyi1wHcyy6FKL5lKVCY1YzEPWViR3w12eNsJRsZq6Yq9+Z2pSaC ZGoOag58b648Wl4dBhoQz0Ma31nHp/zLs9jKCvuZxy/Xitn+e3Zw3RDePHRozXdMbjwg +hXdIpvPRn2YaSQ6Rv8c2FyC3ZmuMjomZr8jMjvPDEcCG5SZvTuyZzYEGN8gpD5luD8G heKQ== X-Gm-Message-State: AOJu0YwIRWpzpElBR+iDKn8vCj6cWTE4/tiIMZ+2WAxMISJdwM+ByX2t bVD1cv56XMPa1tnahNO4eIPG6aRfOPeMcUomhmKS5LLGotsQXFxywHMW3xtNbcJ4tz+atjhkBZF Zo9w7U1tCR6xvTddHh7f3obL4XH9RD0x/F1sapKp28WD95+E= X-Gm-Gg: ASbGncv2ttndUMheA0ANf/+LY7MHxhHzEy6mKHT352HIVR+4nZBFdboi2sxet2ymHeD l7ZLO4MkSx5COJkxtt+8vqVNM+4cYTnQXYlwsQNL9gK2Bvq0nXwr7zImSIb4+XBe/3QvZusF7D9 rKx0pRjgC7ERkNcDrZhvOFrgt7iWihmexfQeefZrFjlJWMUHbJwBBoWc08A+M= X-Google-Smtp-Source: AGHT+IEmYbvwd1XKAL2/kEm4CmZwQiUQGTREneq5bHJAImCPbfYteSQEEtH4QL7Tx+21r4h7VlpU7h/w5aJ0u4SqMuw= X-Received: by 2002:a05:6902:2484:b0:e63:6ebc:e551 with SMTP id 3f1490d57ef6-e6374c811d1mr26337531276.40.1741866111739; Thu, 13 Mar 2025 04:41:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Yogesh Mahajan Date: Thu, 13 Mar 2025 17:11:15 +0530 X-Gm-Features: AQ5f1JrCgpMgXU2dpVbiYY_zG6qm9-y3hYjp1Or76jQpo_ZJq8aFj_gw9m5iRQw Message-ID: Subject: Re: Regarding feature #3319 To: Dave Page Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000d6421c063037ce14" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d6421c063037ce14 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Dave, Yes, we can store connection info. We might need to tweak how we create the query tool connections. Thanks for the inputs. Thanks, Yogesh Mahajan EnterpriseDB On Thu, Mar 13, 2025 at 5:07=E2=80=AFPM Dave Page wrote= : > Hi > > On Thu, 13 Mar 2025 at 11:35, Yogesh Mahajan < > yogesh.mahajan@enterprisedb.com> wrote: > >> Hi Dave, >> >> What about the query tools opened with an ad-hoc server, should we just >> open a query tool with data without connections? >> > > Can we not save the connection parameters used in the JSON (excluding the > password that we can prompt for of course)? > > >> >> Thanks, >> Yogesh Mahajan >> EnterpriseDB >> >> >> On Thu, Mar 13, 2025 at 4:59=E2=80=AFPM Dave Page wr= ote: >> >>> 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 = wrote: >>>> >>>>> >>>>> >>>>> 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 f= uture. >>>>>> >>>>> >>>>> 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 >>>>> >>>>> >>> >>> -- >>> 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 > > --000000000000d6421c063037ce14 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Dave,

Yes, we can store connection info. We might need to tweak how=C2=A0we c= reate the query tool connections.
Thanks for the inputs.

Thanks,
Yogesh= Mahajan
EnterpriseDB


On Thu, Mar 13, = 2025 at 5:07=E2=80=AFPM Dave Page <= dpage@pgadmin.org> wrote:
Hi

On Thu, 13 Mar 2025 at 11:35, Yogesh Mahajan <yogesh.mahajan@enterpris= edb.com> wrote:
Hi Dave,

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

Can we not save the connection parameters used in the JSON = (excluding the password that we can prompt for of course)?
=C2=A0=

Thanks,
Yogesh Ma= hajan
EnterpriseDB
<= /font>


On Thu, Mar 13, 2025 at 4:59=E2=80=AFPM D= ave Page <dpage@p= gadmin.org> wrote:
= Hi

On Thu, 13 Mar 2025 at 11:20, Yogesh Mahajan <yogesh.mahajan@enterprisedb.co= m> wrote:
Hi Dav= e,

<= /div>
Couple o= f follow up questions -=C2=A0

Thanks,
Yogesh Mahaj= an
EnterpriseDB


On Thu, Mar 13, 2025 at 4:37=E2=80=AFPM Dave= Page <dpage@pgad= min.org> wrote:


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

Couple of more questions arose during discussion -=C2=A0

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

Yes :-). Ideally, as much of the original state= as possible should be restored.=C2=A0
<= br>
So, should we open the psql without data and schema diff without compariso= n results?

I don= 9;t see that we have any choice for psql. We absolutely should *not* attemp= t to automatically re-run user queries.

For the sc= hema 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 query tools open with an a= d-hoc server, should=C2=A0we just open a query tool with data without=C2=A0= connections?

=C2=A0
2.Can we use an existing crypt key to encrypt the query data or s= imply json encoding should be enough?
<= div>
We're already storing the query history, so we shoul= d follow the precedent there.
Currently we are storing this data with json encoding done by the request= =C2=A0module.



--


--
--000000000000d6421c063037ce14--