Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qJuyF-0008FM-Io for pgsql-general@arkaria.postgresql.org; Thu, 13 Jul 2023 11:58:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qJuyE-0007gW-2C for pgsql-general@arkaria.postgresql.org; Thu, 13 Jul 2023 11:58:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qJuyD-0007gN-Nb for pgsql-general@lists.postgresql.org; Thu, 13 Jul 2023 11:58:53 +0000 Received: from ms11p00im-qufo17281501.me.com ([17.58.38.52]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qJuy9-000BPG-L3 for pgsql-general@lists.postgresql.org; Thu, 13 Jul 2023 11:58:52 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=1a1hai; t=1689249527; bh=Z04AycH4Dw6q5kbIgEpzsvJF7HJhhzz2L/7v6fDRA7k=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To; b=c+qjoU4VqgXwU3bbox+nVCgzvH6zmkdW0vPKScXNdlPW7nJhAYUXvJm0OuQexCAuT LyZbfkb3uxSvmucPngBHw1lvFFB8XaB+mM0SxuLY03yodiK5FRY7cGQiu3mMtpZ112 Flt/X4yHZ9Ex0V2sK/zDfvqZyeHE7KQiwbU/c6bmPEPpIAeBBE6Umg/977kVG71tPM 1dxzH6wR0LMbxBeJJWJO9UoH3D6iUyBn+oJxaUEqmhgo65VUgxjhwB7lHDc34MA0Fk 9CR7+B6Yln5SIN4RXuS6yTCA8Gf1Ej1Kt8frb+xlxjjB9h00bayL04BMUv0XRwVnCw 67mWAP/8X7TtA== Received: from smtpclient.apple (ms11p00im-dlb-asmtpmailmevip.me.com [17.57.154.19]) by ms11p00im-qufo17281501.me.com (Postfix) with ESMTPSA id 28EC0B61B0E; Thu, 13 Jul 2023 11:58:46 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: Problem perhaps after upgrading to pgadmin4 7.4 From: Carl Erik Eriksson In-Reply-To: Date: Thu, 13 Jul 2023 13:58:33 +0200 Cc: pgsql-general@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <1348D120-AA29-486A-B587-635392893A0D@mac.com> References: <71E975C3-68C5-4CB7-9666-7C23C73BB98F@mac.com> To: depesz@depesz.com X-Mailer: Apple Mail (2.3731.600.7) X-Proofpoint-GUID: bg7DcEJrmdDImI5C9p8ldeAA-CIRLs6A X-Proofpoint-ORIG-GUID: bg7DcEJrmdDImI5C9p8ldeAA-CIRLs6A X-Proofpoint-Virus-Version: =?UTF-8?Q?vendor=3Dfsecure_engine=3D1.1.170-22c6f66c430a71ce266a39bfe25bc?= =?UTF-8?Q?2903e8d5c8f:6.0.425,18.0.816,17.0.605.474.0000000_definitions?= =?UTF-8?Q?=3D2022-01-18=5F01:2022-01-14=5F01,2022-01-18=5F01,2020-01-23?= =?UTF-8?Q?=5F02_signatures=3D0?= X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=946 bulkscore=0 suspectscore=0 spamscore=0 clxscore=1011 adultscore=0 phishscore=0 mlxscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2307130105 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thanks - it seems we might be on pg 10.17-1 /Carl > On 13 Jul 2023, at 13:52, hubert depesz lubaczewski = wrote: >=20 > On Thu, Jul 13, 2023 at 01:20:03PM +0200, Carl Erik Eriksson wrote: >> If I enter a query like select count(*) from table_1 I get a = correct response from the server >> If I enter select * from table_1 I get an error message that I do not = understand: >> Error Message:missing FROM-clause entry for table "rel" >> LINE 8: ...ER JOIN pg_catalog.pg_constraint con ON = con.conrelid=3Drel.oid >> PSQL tool (PGadmin on my Mac) >> However if I enter the same from the PSQL tool I get the correct = output. >>=20 >> But that output goes to my screen and I have found no way of = directing it to a file on my Mac. >>=20 >> Any suggestions? Either getting rid of the error message and getting = the output to my screen within the Query tool where I can then dump the = output to a file >> OR a way of running my query using the PSQL tool and redirecting the = output to a file on my computer. >>=20 >> An amateur who is up a creek without any paddle.. >=20 > Which pg version you're on? >=20 > Generally, try updating to newest pgadmin, from git repo > (https://github.com/pgadmin-org/pgadmin4/), there is/was a bug that > caused problems when using pg < 11 : > = https://github.com/pgadmin-org/pgadmin4/commit/732bcc2b4d91f0126cf69d69c14= df199bc4106bc >=20 > Best regards, >=20 > depesz >=20