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 1tsgPJ-004Zds-OB for pgadmin-hackers@arkaria.postgresql.org; Thu, 13 Mar 2025 11:07:21 +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 1tsgPI-00Ap8g-HZ for pgadmin-hackers@arkaria.postgresql.org; Thu, 13 Mar 2025 11:07:20 +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 1tsgPI-00Ap8Y-A9 for pgadmin-hackers@lists.postgresql.org; Thu, 13 Mar 2025 11:07:20 +0000 Received: from mail-lf1-x12c.google.com ([2a00:1450:4864:20::12c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tsgPE-002dY9-1J for pgadmin-hackers@postgresql.org; Thu, 13 Mar 2025 11:07:19 +0000 Received: by mail-lf1-x12c.google.com with SMTP id 2adb3069b0e04-54954fa61c9so961878e87.1 for ; Thu, 13 Mar 2025 04:07:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1741864037; x=1742468837; 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=a8KQ/boyXPHUK3sWy4WYdjpwE3P5plV1If0iazxYjVo=; b=Rk//ztlyAqmDk8sivvUHVigAEgXujpdOT5/3ZFhpD4nxncpZ0YD91zJ9shhEVevLOP r2oFgij5BHWTBoposqV4nCXzcEYq1FNcAHyzc4s2ZNQkeuPofmLohRrW+cqMDKaW1rmv SKxzPhZ6AFc8xlhKj99/livgdNCcKh7kMd5yjw3+E9CCT1pO9GNfaR01WUI8ucd5MR12 1V2MGBf7OsWY5us/6XWBxR07CE9hL7oIP/BjrrDWPOA0wxBG+MEXIeFdN7p8VEm09xWM EVdXysC7Q/WR7Uh9cT/sXrzTng08HGK2XFjmq0jgrEI326k4pdLlCzckDwwFXlL2VRfw AGqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741864037; x=1742468837; 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=a8KQ/boyXPHUK3sWy4WYdjpwE3P5plV1If0iazxYjVo=; b=TcQ60KVmgiGhaazg9v74nhj6ks7IIaTil7xxU490CWFtEarAq9+Fw/eDjW0cB+7BBt JvnuJzW3p1bod4E7RUwlR2uaIq+v5FCJ7IDBrK2ViVQA8CxeQYE90dL5xDgb64dPeFfv gSnn6o+PZZDZRMcQqn9nFd6O2eFgreVhiSbivZ7SqRtdaJQDWW5wUSkmA7ed0ZwKM60f 9FmnwMOGzpbN4sP4z2N8HoVvcW/40LvtmuNYZ6C3fjfLLkUn6OMEeug1sE1qQKI91Ahr rOiyW0YWS4oJ387JeBIYhGqmPqyk4b0sANlfsccil0L+ZaMOCKbB40TaL2NS7VO4TlOg 3wRg== X-Gm-Message-State: AOJu0YyyfSHMPip5WpdpysPev6ShSsH5QxRlpzt011JCahPP0jmeqYsw pr3x+0Gs+4UxqJUTjF9zMVyTjOKg8+GA5qXjfGOvPpTVPfgT3TZxzNKAHlXfJUCdsvYX/mx/5z6 bmo6pCkmI8K8cgI/E9Ca4cEe3+F/ua/wjgBcocAyEawK5I/ge3Q== X-Gm-Gg: ASbGncuGMoBaXktrayR1s0MCsdjPVuGCQMCzCQ8Zo7cjYNpxRO7evMqp1UA9VHHDIGp SYfVracyXbqivgaGm5CKdG/+hZqOjlPXR5VbkjRXM9YK4TsMASJ+65vAM0wqC7FyNLvVmWYXRRF GRydASdHhoD9rAHmiTnbggjTIeqy53 X-Google-Smtp-Source: AGHT+IHkp6NAG6cB71UrY9spC+Cww6nrk6/o8sohKrJ0KIgIHZNbCUrqkw56wMVyiLhfXiqFzT8iUXoI4wQC6Rtj/Bg= X-Received: by 2002:a05:6512:68d:b0:549:7145:5d24 with SMTP id 2adb3069b0e04-549910b7c48mr8572906e87.46.1741864036656; Thu, 13 Mar 2025 04:07:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Thu, 13 Mar 2025 11:07:05 +0000 X-Gm-Features: AQ5f1JpowiXVbJcPWAoN0tL-QXW0_F-jGZ-diBSHmPaT8dwZm5C3Np0dMLVHrzo Message-ID: Subject: Re: Regarding feature #3319 To: Yogesh Mahajan Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000002709f2063037537d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002709f2063037537d Content-Type: text/plain; charset="UTF-8" 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. > 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. -- Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org pgEdge: https://www.pgedge.com --0000000000002709f2063037537d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


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

Couple of more questions arose during di= scussion -=C2=A0

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

Yes :-). Ideally, = as much of the original state as possible should be restored.=C2=A0
=C2=A0
2.Can we use an e= xisting crypt key to encrypt the query data or simply json encoding should = be enough?

We'r= e already storing the query history, so we should follow the precedent ther= e.

--
--0000000000002709f2063037537d--