Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i6brU-0000tY-Qw for pgsql-sql@arkaria.postgresql.org; Sat, 07 Sep 2019 14:38:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i6brR-0003sw-C9 for pgsql-sql@arkaria.postgresql.org; Sat, 07 Sep 2019 14:38:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i6brQ-0003mM-U9 for pgsql-sql@lists.postgresql.org; Sat, 07 Sep 2019 14:38:45 +0000 Received: from mail-pg1-x541.google.com ([2607:f8b0:4864:20::541]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i6brO-00033T-LU for pgsql-sql@lists.postgresql.org; Sat, 07 Sep 2019 14:38:44 +0000 Received: by mail-pg1-x541.google.com with SMTP id l21so5186647pgm.3 for ; Sat, 07 Sep 2019 07:38:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jv//Q0RUTbGN3cfzBuWTZFLALggsNLzwriNImKqmSg8=; b=LKgOLHbGczzcDRrVa4T3XbTEf5pJTgWEoiEVNvscykRf1u2/T9YqLA4jzmK5VzUOoz 6aY9B9P28YmMUeTweMhJyA1LVbahZkwcc/bE1iD64t3AhN6nsWGYJfEZslygBuaxQ9+Z jrwzcRVIptOSJCN7M5HLAtF2LTfYTftVYfRqNT47f+v1ozAyytojVQvsmJHmquZ7rMWV WNhuKpshAgZg6LTZhd2VC/X1KqtkmzHdzvaC/vmktBWpCHImiSr7cObU2hc0S+NaaNsO fEp3mMhItLoctgTTQ4rN8LMwFVANxHMMwUohgDmANfMXKH5s2IiIgQ1nBGBHvxuZ0b4W nKMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jv//Q0RUTbGN3cfzBuWTZFLALggsNLzwriNImKqmSg8=; b=UlJoi6LAqzlb4nXljXCKreULpUqJk0I8X/nZM9vV7ps94VwlbfS6APAWbQMOErx/Tr gwt+o1klgPIUXEAuFmsQPogGArifRaEu+L+PWCaFcSKGeBXsXFagAfmrDjKkrEUxe2qQ Aq5jqcClM+5hxAV+AIIiWXjyXQixgS9x1YsGSpzqRcU5P+7qxvDLr4UgNI27f+FBjiOj PGTKyhX9nw3bkoDOpvHdDGhLTl0+6r4jeEUlJYlgtbNEqEbnQiDKfNnmMs9mjN+G688E ebWu3Wq5jw6QZfWS/s9s+ajEnlOs1KZ37TXJ22btI73kqLYhwRQK6yV93KT9ZhNWdMb/ hrZg== X-Gm-Message-State: APjAAAUe1nplfJdaAhv2e465IgIwFH4HhIXXV8SInsIj3UEzgly/D6XZ YMKgs6HWlVsTDiq7oz9qRz4+10nrtAjK8w== X-Google-Smtp-Source: APXvYqx2YAYl+cYmptwoFZyUqYDqRrbKSPwiwnTxQ5HXwWygGLxSpkH6MnMbBIsTsiwSsTm5h5psRw== X-Received: by 2002:a62:3893:: with SMTP id f141mr1197015pfa.221.1567865275935; Sat, 07 Sep 2019 07:07:55 -0700 (PDT) Received: from [192.168.1.13] (xplr-208-114-165-80.xplornet.com. [208.114.165.80]) by smtp.gmail.com with ESMTPSA id b16sm1514034pfb.54.2019.09.07.07.07.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 07 Sep 2019 07:07:55 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: How do I enabled Windows 10 to be able to run PSQL etc From: Rob Sargent X-Mailer: iPhone Mail (16G77) In-Reply-To: <207445330.2444743.1567859173939@mail.yahoo.com> Date: Sat, 7 Sep 2019 07:07:49 -0700 Cc: pgsql-sql@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <27D5F961-0A53-4819-9558-B2C685D0AB30@gmail.com> References: <207445330.2444743.1567859173939@mail.yahoo.com> To: Karen Goh List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On Sep 7, 2019, at 5:26 AM, Karen Goh wrote: >=20 > Hello experts, >=20 > Ever since I found out I have a different versions of Postgresql residing i= n my PC, I have deleted the old version - 10 and 7 altogether and installed v= ersion 11. >=20 > So, all look good except that I can't use PSQL at all. >=20 > Then, I found out that there is a security tied to using PSQL in Windows 1= 0. However, I tried to alter the setting for DESKTOP user to Full-Control I c= an't find a way to do it. Neither can I find anything from the internet. >=20 > Please advise how do I alter the setting so that I can use PSQL freely. =20= >=20 > I had tried to use runpsql.batch after reading a Stackoverflow user advice= . >=20 > But, when I tried to do some psql comments, it doesn't work. >=20 > What is that comment you might ask - which is my next problem - this comme= nt is to allow me to merge a table which I have created in PGAdmin 4 into a s= chema - membership which has 3 tables there already. >=20 > The thing is that I found that the table which I have created, it is not a= ble to appear under the schema - memberships. But, when I used runpsql.batc= h, and use /l , it will show up as a table but under postgres. >=20 > Now, in my PGAdmin 4, I did not create a user name either, it is also usin= g postgres as user name so why is the table not appear as a table even after= I refreshed. >=20 > So, I hope someone can tell me the solutions to the above problem. >=20 > Thanks & regards, > Karen >=20 >=20 Without a user everything will be owned by Postgres account but that=E2=80=99= s ok.=20 By =E2=80=98under postgres=E2=80=99 do you mean owned by Postgres in the pub= lic schema or in the postgres database. If the latter then your pgadmin conn= ection settings need the name of the database to use. Your table needs to be= fully qualified by adding the schema name: create table schema.table You can use the alter table statement to reset the schema for the existing t= able or drop table/create table if that=E2=80=99s easier for you.=20=