On Fri, Apr 10, 2015 at 2:14 PM, Michael Paquier
wrote:
> On Fri, Apr 10, 2015 at 6:39 PM, Magnus Hagander wrote:
> >> +typedef struct PgBackendSSLStatus
> >> +{
> >> +/* Information about SSL connection */
> >> +int ssl_bits;
> >> +boolssl_compress
On Thu, Apr 9, 2015 at 5:46 PM, Andres Freund wrote:
> On 2015-04-09 15:56:00 +0200, Magnus Hagander wrote:
> > On Thu, Apr 9, 2015 at 3:20 PM, Andres Freund
> wrote:
> >
> > > Hi,
> > >
> > > On 2015-04-09 13:31:55 +0200, Magnus Hagander wrote:
> > > > +
> > > > +
> > >
> pg_stat_sslpg_st
On 2015-04-09 15:56:00 +0200, Magnus Hagander wrote:
> On Thu, Apr 9, 2015 at 3:20 PM, Andres Freund wrote:
>
> > Hi,
> >
> > On 2015-04-09 13:31:55 +0200, Magnus Hagander wrote:
> > > +
> > > +
> >
> > pg_stat_sslpg_stat_ssl
> > > + One row per connection (regular and replication),
On Thu, Apr 9, 2015 at 3:20 PM, Andres Freund wrote:
> Hi,
>
> On 2015-04-09 13:31:55 +0200, Magnus Hagander wrote:
> > +
> > +
>
> pg_stat_sslpg_stat_ssl
> > + One row per connection (regular and replication), showing
> information about
> > +SSL used on this connection.
>
Hi,
On 2015-04-09 13:31:55 +0200, Magnus Hagander wrote:
> +
> +
> pg_stat_sslpg_stat_ssl
> + One row per connection (regular and replication), showing
> information about
> +SSL used on this connection.
> +See for details.
> +
> +
> +
I kinda wo
On Wed, Dec 17, 2014 at 9:19 PM, Heikki Linnakangas wrote:
> On 11/19/2014 02:36 PM, Magnus Hagander wrote:
>
>> + /* Create or attach to the shared SSL status buffers */
>> + size = mul_size(NAMEDATALEN, MaxBackends);
>> + BackendSslVersionBuffer = (char *)
>> + S
On Fri, Feb 13, 2015 at 5:31 PM, Magnus Hagander wrote:
>
> On Fri, Feb 13, 2015 at 9:07 AM, Michael Paquier
> wrote:
>
>> Magnus, are you planning to work on this item of your shame list soon?
>> Could you clarify the status of this patch?
>
>
> I do, and I hope to work on it over the next week o
On Fri, Feb 13, 2015 at 9:07 AM, Michael Paquier
wrote:
>
>
> On Tue, Feb 3, 2015 at 9:36 PM, Magnus Hagander
> wrote:
>
>>
>> On Tue, Feb 3, 2015 at 6:42 AM, Michael Paquier <
>> michael.paqu...@gmail.com> wrote:
>>
>>> Where are we on this patch? No new version has been provided and there
>>>
On Tue, Feb 3, 2015 at 9:36 PM, Magnus Hagander wrote:
>
> On Tue, Feb 3, 2015 at 6:42 AM, Michael Paquier > wrote:
>
>> Where are we on this patch? No new version has been provided and there
>> have been comments provided by Heikki here
>> (5491e547.4040...@vmware.com) and by Alexei here
>> (87
On Tue, Feb 3, 2015 at 6:42 AM, Michael Paquier
wrote:
> Where are we on this patch? No new version has been provided and there
> have been comments provided by Heikki here
> (5491e547.4040...@vmware.com) and by Alexei here
> (87ppbqz00h@commandprompt.com).
>
>
Yeah, it's on my shame list. I
Where are we on this patch? No new version has been provided and there
have been comments provided by Heikki here
(5491e547.4040...@vmware.com) and by Alexei here
(87ppbqz00h@commandprompt.com).
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Mon, Jan 5, 2015 at 9:56 PM, Peter Eisentraut wrote:
> On 11/19/14 7:36 AM, Magnus Hagander wrote:
> > +
> > +
>
> pg_stat_sslpg_stat_ssl
> > + One row per connection (regular and replication), showing
> statistics about
> > +SSL used on this connection.
> > +See
On 11/19/14 7:36 AM, Magnus Hagander wrote:
> +
> +
> pg_stat_sslpg_stat_ssl
> + One row per connection (regular and replication), showing
> statistics about
> +SSL used on this connection.
> +See for details.
> +
> +
> +
It doesn't really show "s
On 11/19/2014 02:36 PM, Magnus Hagander wrote:
+ /* Create or attach to the shared SSL status buffers */
+ size = mul_size(NAMEDATALEN, MaxBackends);
+ BackendSslVersionBuffer = (char *)
+ ShmemInitStruct("Backend SSL Version Buffer", size, &found);
+
+ if (!
Magnus Hagander writes:
>>
>> You should add it to the next CF for proper tracking, there are already many
>> patches in the queue waiting for reviews :)
>
> Absolutely - I just wanted those that were already involved in the
> thread to get a chance to look at it early :) didn't want to submit it
On Tue, Nov 11, 2014 at 1:04 AM, Michael Paquier
wrote:
> On Tue, Nov 11, 2014 at 1:43 AM, Magnus Hagander
> wrote:
>>
>> Right now it just truncates the dn at NAMEDATALEN - so treating it the
>> same as we do with hostnames. My guess is this is not a big problem
>> because in the case of long DN
On Tue, Nov 11, 2014 at 1:43 AM, Magnus Hagander
wrote:
> Right now it just truncates the dn at NAMEDATALEN - so treating it the
> same as we do with hostnames. My guess is this is not a big problem
> because in the case of long DNs, most of the time the important stuff
> is at the beginning anyw
On Mon, Jul 21, 2014 at 5:24 PM, Bernd Helmle wrote:
>
>
> --On 12. Juli 2014 15:08:01 +0200 Magnus Hagander
> wrote:
>
>> Before doing that, however, I'd like to ask for opinions :) The hack
>> currently exposes a separate view that you can join to
>> pg_stat_activity (or pg_stat_replication) on
--On 12. Juli 2014 15:08:01 +0200 Magnus Hagander
wrote:
Before doing that, however, I'd like to ask for opinions :) The hack
currently exposes a separate view that you can join to
pg_stat_activity (or pg_stat_replication) on the pid -- this is sort
of the same way that pg_stat_replication
On Mon, Jul 14, 2014 at 7:54 PM, Stefan Kaltenbrunner
wrote:
> On 07/13/2014 10:35 PM, Magnus Hagander wrote:
>> On Sun, Jul 13, 2014 at 10:32 PM, Stefan Kaltenbrunner
>> wrote:
>>> On 07/12/2014 03:08 PM, Magnus Hagander wrote:
As an administrator, I find that you fairly often want to know
On 07/13/2014 10:35 PM, Magnus Hagander wrote:
> On Sun, Jul 13, 2014 at 10:32 PM, Stefan Kaltenbrunner
> wrote:
>> On 07/12/2014 03:08 PM, Magnus Hagander wrote:
>>> As an administrator, I find that you fairly often want to know what
>>> your current connections are actually using as SSL paramete
On Sun, Jul 13, 2014 at 10:32 PM, Stefan Kaltenbrunner
wrote:
> On 07/12/2014 03:08 PM, Magnus Hagander wrote:
>> As an administrator, I find that you fairly often want to know what
>> your current connections are actually using as SSL parameters, and
>> there is currently no other way than gdb to
On 07/12/2014 03:08 PM, Magnus Hagander wrote:
> As an administrator, I find that you fairly often want to know what
> your current connections are actually using as SSL parameters, and
> there is currently no other way than gdb to find that out - something
> we definitely should fix.
Yeah that wo
On Sat, Jul 12, 2014 at 4:36 PM, Tom Lane wrote:
> Magnus Hagander writes:
>> As an administrator, I find that you fairly often want to know what
>> your current connections are actually using as SSL parameters, and
>> there is currently no other way than gdb to find that out - something
>> we de
Magnus Hagander writes:
> As an administrator, I find that you fairly often want to know what
> your current connections are actually using as SSL parameters, and
> there is currently no other way than gdb to find that out - something
> we definitely should fix.
I'm wondering whether it's such a
As an administrator, I find that you fairly often want to know what
your current connections are actually using as SSL parameters, and
there is currently no other way than gdb to find that out - something
we definitely should fix.
You can find it out today through libpq (the PQgetssl functions), t
26 matches
Mail list logo
