Re: What is wrong with my pgadmin?

2018-03-05 Thread Murtuza Zabuawala
Hello,

This is a bug with pgAdmin4 (Bug: RM#3090
<https://redmine.postgresql.org/issues/3090>).

Work around for this problem is to set
lc_messages = 'en_US.UTF-8'
in "postgresql.conf" file.


--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


On Mon, Mar 5, 2018 at 7:57 PM, Martin Moore 
wrote:

> Using pgAdmin 4 2.0 on pg 9.6 and 10 I get div/0 error.
>
>
>
> On 05/03/2018, 14:22, "Adrian Klaver"  wrote:
>
> On 03/05/2018 06:05 AM, Łukasz Jarych wrote:
> > Hi Guys,
> >
> > what is wrong with my pgAdmin?
> >
> > I am creating wrong query:
> >
> > select 1/0 but still this is executed!
>
> Well it will be executed, but it should throw an error. Can you confirm
> that running select 1/0; in psql does indeed throw an error:
>
> test=# select 1/0;
> ERROR:  division by zero
>
> Also:
>
> 1) What version of pgAdmin4 are you running?
>
> 2) What version of Postgres is it running against?
>
> >
> >
> >
> > why?
> >
> > Best wishes,
> > Jacek
> >
> >
>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>
>
>
>
>
>


Re: Does pgadmin4 work with postgresql 8.4?

2019-08-05 Thread Murtuza Zabuawala
No, pgAdmin4 only supports PostgreSQL 9.2 and later versions.

On Tue, 6 Aug 2019, 01:45 Benedict Holland, 
wrote:

> The subject says it all. I am using a very old database that I cant
> upgrade. Do I have to manage it with pgadmin3 or can I use postgresql 4?
>

> Thanks,
> ~Ben
>


Re: Does pgadmin4 work with postgresql 8.4?

2019-08-05 Thread Murtuza Zabuawala
On Tue, Aug 6, 2019 at 7:57 AM Adrian Klaver 
wrote:

> On 8/5/19 7:04 PM, Murtuza Zabuawala wrote:
> > No, pgAdmin4 only supports PostgreSQL 9.2 and later versions.
>
> Where is that mentioned in the documentation?
>

It is mentioned on the front page of https://www.pgadmin.org/
(Check introduction texts on the elephant wallpaper)

-- Murtuza


>
> >
> > On Tue, 6 Aug 2019, 01:45 Benedict Holland,
> > mailto:benedict.m.holl...@gmail.com>>
> wrote:
> >
> > The subject says it all. I am using a very old database that I cant
> > upgrade. Do I have to manage it with pgadmin3 or can I use
> postgresql 4?
> >
> >
> > Thanks,
> > ~Ben
> >
>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>


Re: the installation of pgadmin4 makes me weep in frustration

2019-01-14 Thread Murtuza Zabuawala
Thanks to Postgres Debian/Ubuntu packaging team, Installing pgAdmin4 is
straightforward task,

1) Create the file /etc/apt/sources.list.d/pgdg.list and add a line for the
repository
deb http://apt.postgresql.org/pub/repos/apt/ bionic-pgdg main

2) Import the repository signing key, and update the package lists
wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo
apt-key add -

3) sudo apt-get update

4) sudo apt-get install pgadmin4

Check https://www.postgresql.org/download/linux/ubuntu/ for more
information.

--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



On Mon, Jan 14, 2019 at 1:29 PM robert  wrote:

> Hi There
>
>
> first, thanks a lot for the great an beautiful software we get from
> PostgreSQL and all people around it.
>
> But I wonder how it comes, that installing pgadmin4 is so incredibly hard?
>
> And no documentation.
>
> I would like to install pgadmin4 to my ubuntu 18.1 laptop.
>
> Where do I find doku on how to install pgadmin4. Preferably I would like
> to install it using pip?
>
>
> thanks
>
> robert
> --
> Robert Rottermann CEO
>
> 031 333 10 20
> rob...@redo2oo.ch
> Sickingerstrasse 3, 3014 Bern
> <http://maps.apple.com/?q=Sickingerstrasse%203,3014%0D%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20Bern>
>
> [image: https://Redo2oo.ch] <https://redo2oo.ch>
> *Ihr Partner wenn es um ERP Lösungen geht.*
>


Re: Forks of pgadmin3?

2019-03-22 Thread Murtuza Zabuawala
On Fri, Mar 22, 2019 at 9:55 PM  wrote:

> This is probably my 10th attempt to move from pgadminIII to pgadmin4. At
> least the performance has significantly improved over time and seems now
> acceptable.
>
> The biggest drawback is however that all elements are locked up in one
> browser window – I cannot find any option to detach a query windows and put
> it on a different monitor.
>

Opening Query tool or Debugger window in a new separate browser window is
configurable option in pgAdmin4, Goto

File -> Preferences -> Query Tool -> Display -> Open in new browser tab
Set it to: True

File -> Preferences -> Debugger-> Display -> Open in new browser tab
Set it to: True

Screenshot of option: https://imgur.com/a/yhs8mtP

-- Murtuza


> 95% of my time I use pgadminIII just to type select and update statements
> and review the output rows.
>
> I know that I can do this in psql but it’s not handy with many columns.
>
> For that reason we currently stay with pgadminIII (and this is for us also
> one of several reasons to delay any move from 9.6 to a more recent version).
>
>
>
> Klaus
>
>
>
> *Von:* Tony Shelver 
> *Gesendet:* Freitag, 22. März 2019 15:34
> *Cc:* PG-General Mailing List 
> *Betreff:* Re: Forks of pgadmin3?
>
>
>
> Or just persevere with pgadmin4 for a few months?   Pretty common for
> people to hate any major changes to a tool that they are very comfortable
> with.
>
>
>
> This year I've invested the time to learn a few new toolsets (not on
> Postgresql necessarily) and found it to be well worth while.
>
>
>
> At least pgAdmin4 is up to date with all the new features in 11.
>


Re: Case Insensitive

2019-03-28 Thread Murtuza Zabuawala
On Thu, Mar 28, 2019 at 1:50 PM Sridhar N Bamandlapally <
sridhar@gmail.com> wrote:

> Hi PG-General and Pgsql-Admin
>
> Can we achieve CASE INSENSITIVE in PostgreSQL?
>

You can try
*select * from emp where ename *ILIKE *'aaa';*


>
> I mean, need below way
>
> postgres=# select * from emp;
>  eid | ename
> -+---
>1 | aaa
>2 | AAA
> (2 rows)
>
>
>
> *postgres=# select * from emp where ename='aaa';*
> * eid | ename*
> *-+---*
> *   1 | aaa*
> *   2 | AAA*
> *(2 rows)*
> *--above result is just an manual made example only*
>
>
> Thanks
> Sridhar
>
>


Re: unsubscribe

2017-11-20 Thread Murtuza Zabuawala
On Tue, Nov 21, 2017 at 12:49 PM, Craig Ringer 
wrote:

> On 21 November 2017 at 15:17, Rafal Pietrak  wrote:
>
>> Hi all,
>>
>> Have anyone noticed, that last couple of days on the list, can become a
>> nice example of HOWTO turn the best list on the planet into a nightmare?
>>
>> Pls forgive rudeness, but IMHO, whoever made the "upgrade" should
>> manually take all the "unsubscribe" messages from archive and do that
>> "unsubscription" by hand  instead of giving not always helpfull
>> guidance.
>
>
> The list used to have a filter that blocked messages with "unsubscribe" in
> the subject or forced them into moderation the moderation queue.
>
> I thought that'd be preserved with the PgLister migration.
>
> But really, a nightmare? Yeah, it's a pain, but I think that's laying it
> on a bit strong. Personally I appreciate the hard and usually thankless
> work the infrastructure and admin team do.
>
​+1​


>
>
> --
>  Craig Ringer   http://www.2ndQuadrant.com/
>  PostgreSQL Development, 24x7 Support, Training & Services
>


Re: [GENERAL] Date Time data types

2017-11-23 Thread Murtuza Zabuawala
As per my knowledge,

CLOCK_TIMESTAMP value changes every time you call it even in the
same transaction

BEGIN
  ...
  CLOCK_TIMESTAMP()  -- Gives 2017-11-23 15:02:27.492867+05:30
  ...
  ...
  CLOCK_TIMESTAMP()  -- Gives different time as per current clock time
  ...
END;


CURRENT_TIMESTAMP
​is the time of ​
start of current transaction
​ and does not change in the same transaction.​


BEGIN
  ...
  CURRENT_TIMESTAMP() -- Gives 2017-11-23 15:01:40.171462+05:30
  ...
  ...
  CURRENT_TIMESTAMP() -- Gives same time as previous call
  ...
END;


​-- Murtuza​


On Thu, Nov 23, 2017 at 2:29 PM, Brahmam Eswar 
wrote:

> What is difference between CLOCK_TIMESTAMP() and CURRENT_TIMESTAMP?
>
> Is there any specific use case to differentiate them .
> --
> Thanks & Regards,
> Brahmeswara Rao J.
>


Re: pgadmin4: not possible to create server

2018-02-06 Thread Murtuza Zabuawala
Add following in your pg_hba.conf,

hostall all 0.0.0.0/ 0 md5

restart your Postgres database server and try to connect again from
pgAdmin4.

On Tue, Feb 6, 2018 at 10:54 PM, robert rottermann  wrote:

> Hi there,
>
> I have installed pgadmin4 locally using its docker image.
>
> this i did running the following command:
>
> docker run -p 80:80 -e "PGADMIN_DEFAULT_EMAIL=admin" -e
> "PGADMIN_DEFAULT_PASSWORD=admin" -d dpage/pgadmin4
>
> I then could access it and log into it.
>
> However all my attempts end in:
>
> Unable to connect to server:
>
> could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> could not connect to server: Connection refused
> Is the server running on host "localhost" (127.0.0.1) and accepting
> TCP/IP connections on port 5432?
>
>
> can anybody give me a hint, what to do?
>
> thanks
>
> robert
>
>
> in /etc/postgresql/10/main/postgresql.conf
>
> i have:
>
> #---
> ---
> # CONNECTIONS AND AUTHENTICATION
> #---
> ---
>
> # - Connection Settings -
>
> listen_addresses = '*'  # what IP address(es) to listen on;
> # comma-separated list of
> addresses;
>
>
> and this is my /etc/postgresql/10/main/pg_hba.conf
>
> # DO NOT DISABLE!
> # If you change this first entry you will need to make sure that the
> # database superuser can access the database using some other method.
> # Noninteractive access to all databases is required during automatic
> # maintenance (custom daily cronjobs, replication, and similar tasks).
> #
> # Database administrative login by Unix domain socket
> local   all postgres peer
>
> # TYPE  DATABASEUSERADDRESS METHOD
>
> # "local" is for Unix domain socket connections only
> local   all all trust
> # IPv4 local connections:
> hostall all 127.0.0.1/32 trust
> # IPv6 local connections:
> hostall all ::1/128 trust
> # Allow replication connections from localhost, by a user with the
> # replication privilege.
> local   replication all peer
> hostreplication all 127.0.0.1/32 md5
> hostreplication all ::1/128 md5
>
>
>
>
>