pgAdmin Docker gunicorn configurable --access-logfile

[Seweryn Zeman]

Hi, me and my company is working with pgAdmin since we decided to use pgSql – 
mostly for development with containers. In this case Docker. While starting a 
docker-compose in dev mode with pgAdmin in stack we can see lots of access logs 
for HTTP and WS which are very irrelevant to us. This makes important logs to 
disappear.

Current Docker entrypoint is having launch command set to...

exec gunicorn ... --access-logfile - run_pgadmin:app

…with some parameters easily configurable via env vars.

My proposal is to also make --access-logfile configurable, like:

--access-logfile ${GUNICORN_ACCESS_LOGFILE:--}

This preserves 100% backward compability and allows users like us to set 
GUNICORN_ACCESS_LOGFILE=None or another file or stdout of particular PID.

--
Seweryn Zeman
CTO, Jazzy Innovations

Re: pgAdmin Docker gunicorn configurable --access-logfile

[Aditya Toshniwal]

Hi Seweryn,

Kindly raise a feature request here -
https://redmine.postgresql.org/projects/pgadmin4/issues/new

On Mon, Nov 18, 2019 at 4:59 PM Seweryn Zeman 
wrote:

> Hi, me and my company is working with pgAdmin since we decided to use
> pgSql – mostly for development with containers. In this case Docker. While
> starting a docker-compose in dev mode with pgAdmin in stack we can see lots
> of access logs for HTTP and WS which are very irrelevant to us. This makes
> important logs to disappear.
>
> Current Docker entrypoint is having launch command set to...
>
> exec gunicorn ... --access-logfile - run_pgadmin:app
>
> …with some parameters easily configurable via env vars.
>
> My proposal is to also make --access-logfile configurable, like:
>
> --access-logfile ${GUNICORN_ACCESS_LOGFILE:--}
>
> This preserves 100% backward compability and allows users like us to set
> GUNICORN_ACCESS_LOGFILE=None or another file or stdout of particular PID.
>
> --
> Seweryn Zeman
> CTO, Jazzy Innovations
>


-- 
Thanks and Regards,
Aditya Toshniwal
Sr. Software Engineer | EnterpriseDB India | Pune
"Don't Complain about Heat, Plant a TREE"

pgpool High Availability Issue

[a venkatesh]

Hi,

I'm working on configuring high availability for pgpool using watchdog.
Initially, I tried with two pgpool nodes (along with a pgmaster and
pgslave). In this scenario, assuming pgpool node 1 was started first and
became the leader. After sometime , the node got disconnected with  pgpool
node 2 and pgpool node 2 as well declared itself as leader.


To handle this kind of scenario, I tried provisioning an additional pgpool
node and made a cluster with total 5 nodes (3 pgpool nodes, 1 pgmaster and
1 pgslave), assuming it will create a quorum to handle such situations.
Unfortunately, the situation still remains the same. (In case of any
disconnection between node that became leader and the first stand by node,
both the nodes try to manage the pgmaster and slave simultaneously).

Please help me understand if this is expected behavior or some additional
configurations are required to be made, so that two pgpool nodes don't
become leader simultaneously.  If it's an expected behavior, how can we
handle this ?

(A point to note is that I'm not using elastic IP address here, instead I
have created a network load balancer in AWS, created a target group with
all the three pgpool nodes as targets).

Regards,

[pgAdmin][RM4696] Add RE-SQL/MSQL test cases for Materialized View

[Rahul Shirsat]

Hi Hackers,

I have attached the patch for RE-SQL/MSQL test cases for View as well as
Materialized View.

-- 
*Rahul Shirsat*
Software Engineer | EnterpriseDB Corporation.


RM4696.patch
Description: Binary data