FYI
This is what I had tried wrt logstash.
https://gist.github.com/cabecada/dd765a30f6946fdbf0bec0eb31fba047
From: Vijaykumar Jain
Date: Friday, March 30, 2018 at 11:33 PM
To: "pgsql-general@lists.postgresql.org"
Subject: Re: Redacting params in PostgreSQL logs
https://github.com/lfittl/pg_q
Hi
I am just setting up a postgres server, details
Host 192.168.0.3
pg_hba.conf
# TYPE DATABASEUSERADDRESS METHOD
# "local" is for Unix domain socket connections only
local all all peer
# IPv4 local connections:
On 3/31/18 11:44, Mike Martin wrote:
> Hi
> I am just setting up a postgres server, details
> Host 192.168.0.3
> pg_hba.conf
> # TYPE DATABASE USER ADDRESS METHOD
>
> # "local" is for Unix domain socket connections only
> local all all
On Sat, Mar 31, 2018 at 11:44 AM, Mike Martin wrote:
> Hi
> I am just setting up a postgres server, details
> Host 192.168.0.3
> pg_hba.conf
> # TYPE DATABASEUSERADDRESS METHOD
>
> # "local" is for Unix domain socket connections only
> local all
Hi all,
it's very simple and intuitive case but let me describe first.
1. session 1 calls pg_advisory_lock(1234) and succeeds.
2. session 2 calls pg_advisory_lock(1234) and stops on waiting.
All fine BUT pid for session2 appears already with backend_xmin in
pg_stat_activity
which means vacuum won't
Hi All!
I've been experimenting with track_functions options and what I've saw it's
really puzzling me.
Documentation says:
/ SQL-language functions that are simple enough to be "inlined" into the
calling query will not be tracked, regardless of this setting./
But it came up, it depends on much
On 03/31/2018 04:40 PM, pinker wrote:
Hi All!
I've been experimenting with track_functions options and what I've saw it's
really puzzling me.
Documentation says:
/ SQL-language functions that are simple enough to be "inlined" into the
calling query will not be tracked, regardless of this setting
Adrian Klaver-4 wrote
> https://www.postgresql.org/docs/10/static/monitoring-stats.html#PG-STAT-USER-FUNCTIONS-VIEW
>
> "...But if you want to see new results with each query, be sure to do
> the queries outside any transaction block. Alternatively, you can invoke
> pg_stat_clear_snapshot(), whi
On 03/31/2018 05:17 PM, pinker wrote:
Adrian Klaver-4 wrote
https://www.postgresql.org/docs/10/static/monitoring-stats.html#PG-STAT-USER-FUNCTIONS-VIEW
"...But if you want to see new results with each query, be sure to do
the queries outside any transaction block. Alternatively, you can invoke
Good morning.
Please suggest the best suited unit test frame work for postgresql database
and also shared the related documents to understand the framework.
--
Regards,
Raghavendra Rao J S V
10 matches
Mail list logo