> pg_hba.conf is "host based access [control]" . I'm not sure it's really the
> right place.
I am open to have another configuration file, say routing_list.conf to define
the routing rules, but felt it is easy to extend the hba conf file.
> But we now have a session-intent stuff though. So we co
> What advantages do you see in doing this in the backend over the current
> system where the concerns are separated, i.e. people use connection poolers
> like pgbouncer to do the routing?
IMHO connection pooler is not great for latency sensitive applications. For
small deployments, proxy is an
Proposal:
Add the ability to the PostgreSQL server instance to route the traffic to a
different server instance based on the rules defined in server's pg_bha.conf
configuration file. At a high level this enables offloading the user requests
to a different server instance based on the rules defin
Tom, Robert, Microsoft is interested in supporting windows SChannel for
Postgres. Please let know how we can help taking this forward. We would love
contributing to this either by enhancing the original patch provided by Heikki,
or test the changes on Windows.
Thanks,
Satya
-Original Messa
Thank you! Got it.
-Original Message-
From: Stephen Frost [mailto:sfr...@snowman.net]
Sent: Monday, September 25, 2017 10:57 AM
To: Magnus Hagander
Cc: Satyanarayana Narlapuram ;
PostgreSQL-development
Subject: Re: [HACKERS] Reading backup label file for checkpoint and redo
location
Hi there,
During crash recovery, last checkpoint record information is obtained from the
backup label if present, instead of getting it from the control file. This
behavior is causing PostgreSQL database cluster not to come up until the backup
label file is deleted (as the error message says).
-Original Message-
From: pgsql-hackers-ow...@postgresql.org
[mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Robert Haas
Sent: Thursday, June 29, 2017 5:18 AM
To: Tom Lane
Cc: Craig Ringer ; Peter Eisentraut ;
Magnus Hagander ; PostgreSQL-development
Subject: Re: protocol versi
quires including full
cluster_name every time user connect to a different database.
Thanks,
Satya
From: Magnus Hagander [mailto:mag...@hagander.net]
Sent: Thursday, June 15, 2017 9:24 AM
To: Tom Lane
Cc: Alvaro Herrera ; Satyanarayana Narlapuram
; pgsql-hackers@postgresql.org
Subject: Re: [H
_name in the startup message and will not be included otherwise.
Thanks,
Satya
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thursday, June 15, 2017 8:58 AM
To: Alvaro Herrera
Cc: Satyanarayana Narlapuram ;
pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Ma
: Tuesday, June 20, 2017 12:44 PM
To: Alvaro Herrera
Cc: Satyanarayana Narlapuram ; Pavel
Stehule ; Daniel Gustafsson ;
PostgreSQL mailing lists
Subject: Re: [HACKERS] Optional message to user when terminating/cancelling
backend
On Tue, Jun 20, 2017 at 11:54 AM, Alvaro Herrera
wrote
+1.
This really helps PostgreSQL Azure service as well. When we are doing the
upgrades to the service, instead of abruptly terminating the sessions we can
provide this message.
Thanks,
Satya
From: pgsql-hackers-ow...@postgresql.org
[mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Pave
-Original Message-
From: Andres Freund [mailto:and...@anarazel.de]
Sent: Friday, June 16, 2017 10:48 AM
To: Tom Lane
Cc: Satyanarayana Narlapuram ;
pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Making server name part of the startup message
On 2017-06-15 09:43:13 -0400, Tom
As a cloud service, Azure Database for PostgreSQL uses a gateway proxy to route
connections to a node hosting the actual server. Potentially there could be
multiple hops (for example client, optional proxy at the client like pgbouncer
for connection pooling, Azure gateway proxy, backend server)
As a cloud service, Azure Database for PostgreSQL uses a gateway proxy to route
connections to a node hosting the actual server. To do that, the proxy needs to
know the name of the server it tries to locate. As a work-around we currently
overload the username parameter to pass in the server name
14 matches
Mail list logo